Lines Matching full:eoi
331 * as a "replay" because EOI decided there was still something in xive_get_irq()
339 * entry (on HW interrupt) from a replay triggered by EOI, in xive_get_irq()
360 * After EOI'ing an interrupt, we need to re-check the queue
372 DBG_VERBOSE("eoi: pending=0x%02x\n", xc->pending_prio); in xive_do_queue_eoi()
378 * EOI an interrupt at the source. There are several methods
387 /* If the XIVE supports the new "store EOI facility, use it */ in xive_do_source_eoi()
394 * For LSIs, we use the "EOI cycle" special load rather than in xive_do_source_eoi()
417 /* irq_chip eoi callback, called with irq descriptor lock held */
427 * EOI the source if it hasn't been disabled and hasn't in xive_irq_eoi()
805 * 11, then perform an EOI. in xive_irq_retrigger()
861 * This saved_p is cleared by the host EOI, when we know in xive_irq_set_vcpu_affinity()
871 * that we *will* eventually get an EOI for it on in xive_irq_set_vcpu_affinity()
912 * interrupt with an EOI. If it is set, we know there is in xive_irq_set_vcpu_affinity()
1064 DBG_VERBOSE("IPI eoi: irq=%d [0x%lx] (HW IRQ 0x%x) pending=%02x\n", in xive_ipi_eoi()
1572 * For LSIs, we EOI, this will cause a resend if it's in xive_flush_cpu_queue()