Lines Matching full:lpi
33 * Creates a new (reference to a) struct vgic_irq for a given LPI.
34 * If this LPI is already mapped on another ITS, we increase its refcount
36 * If this is a "new" LPI, we allocate and initialize a new struct vgic_irq.
69 * check that we don't add a second list entry with the same LPI. in vgic_add_lpi()
75 /* Someone was faster with adding this LPI, lets use that. */ in vgic_add_lpi()
98 * the respective config data from memory here upon mapping the LPI. in vgic_add_lpi()
100 * Should any of these fail, behave as if we couldn't create the LPI in vgic_add_lpi()
275 * Reads the configuration data for a given LPI from guest memory and
382 * Promotes the ITS view of affinity of an ITTE (which redistributor this LPI
399 * Updates the target VCPU for every LPI targeting this collection.
425 * with our own data structures. This relies on the LPI being
724 * Find the target VCPU and the LPI number for a given devid/eventid pair
797 * if the guest has blocked the MSI. So we map any LPI mapping in vgic_its_inject_msi()
1251 * The CLEAR command removes the pending state for a particular LPI.
1343 * afterwards, so we make sure that no LPI is using the associated target_vcpu.
1385 * The INT command injects the LPI associated with that DevID/EvID pair.
1797 /* This is called on setting the LPI enable bit in the redistributor. */
2219 * If an LPI carries the HW bit, this means that this in vgic_its_save_itt()