Lines Matching refs:interrupt

13 interrupt at some point in time.  When such an interrupt is raised, the
14 host OS initially handles the interrupt and must somehow signal this
15 event as a virtual interrupt to the guest.  Another example could be a
18 and KVM must therefore somehow inject a virtual interrupt on behalf of
21 These virtual interrupts corresponding to a physical interrupt on the
33 with the virtual IRQ number and the state of the interrupt (Pending,
35 interrupt, the LR state moves from Pending to Active, and finally to
46 interrupt on the physical distributor when the guest deactivates the
47 corresponding virtual interrupt.
55   - The physical interrupt is acked by the host, and becomes active on
59   - LR.Pending will stay set as long as the guest has not acked the interrupt.
69 distributor before entering the guest, because the interrupt is never actually
71 forwarded interrupts (non-shared) the host does not deactivate the interrupt
72 when the host ISR completes, but leaves the interrupt active until the guest
73 deactivates it.  Leaving the interrupt active is allowed, because Linux
84 Level-triggered interrupts will keep the interrupt line to the GIC
86 line.  This means that the interrupt will remain pending on the physical
89 interrupt will exit the guest as soon as we switch into the guest,
93 the pending interrupt to the CPU.  As soon as the guest deactivates the
94 interrupt, the physical line is sampled by the hardware again and the host
95 takes a new interrupt if and only if the physical line is still asserted.
101 potentially slow down handling of the interrupt in the guest, because a
102 physical interrupt occurring in the middle of the guest ISR would
103 preempt the guest for the host to handle the interrupt.  Additionally,
105 core from that running your VCPU, you still have to interrupt the VCPU
109 the HW bit set, the virtual interrupt is injected and additional
110 physical interrupts occurring before the guest deactivates the interrupt
112 soon as the guest deactivates the interrupt, the host takes another
113 interrupt if and only if there was a physical interrupt between injecting
114 the forwarded interrupt to the guest and the guest deactivating the
115 interrupt.
118 HW bit set, the interrupt must also be active on the physical
157 10. KVM marks the timer interrupt as active on the physical distributor
158 11. KVM injects a forwarded physical interrupt to the guest
161 Notice that KVM injects a forwarded physical interrupt in step 11 without
162 the corresponding interrupt having actually fired on the host.  That is
163 exactly why we mark the timer interrupt as active in step 10, because
179     interrupt because it concludes the timer has expired.
180 7.  KVM marks the timer interrupt as active on the physical distributor
183 Notice that again the forwarded physical interrupt is injected to the
185 is because the physical interrupt is never actually seen by the host because the
186 timer is disabled upon guest return, and the virtual forwarded interrupt is