Lines Matching refs:as

7 OS sees as regular interrupts.  The code is famously known as the VGIC.
15 event as a virtual interrupt to the guest.  Another example could be a
23 referred to as 'virtualized physical interrupts' and 'mapped interrupts'.
59   - LR.Pending will stay set as long as the guest has not acked the interrupt.
60   - LR.Pending transitions to LR.Active on the guest read of the IAR, as
70 handled on the host (see details on the timer as an example below).  For other
89 interrupt will exit the guest as soon as we switch into the guest,
90 preventing the guest from ever making progress as the process repeats
93 the pending interrupt to the CPU.  As soon as the guest deactivates the
100 from a physical device as pure virtual interrupts.  But that would
111 simply mark the state on the physical distributor as Pending+Active.  As
112 soon as the guest deactivates the interrupt, the host takes another
125 active state.  They become pending when a device signal them, and as
126 soon as they are acked by the CPU, they are inactive again.
129 for physical LPIs that are forwarded to a VM as virtual interrupts,
157 10. KVM marks the timer interrupt as active on the physical distributor
163 exactly why we mark the timer interrupt as active in step 10, because
180 7.  KVM marks the timer interrupt as active on the physical distributor