On 07/30/2009 02:16 PM, Gleb Natapov wrote:
I think there's little reason now. One thing we need to do is make it
possible to call the injection code twice without entering the guest. I
think right now it assumes nothing has been injected.
I Looked at this and it seems the current code handle this case.
Injection puts an event on a queue and if we haven't entered a guest
after this point on the next entry event is injected from the queue,
just like if injection failed due to IDT access.
Good (it was one of the goals of the original interrupt rework, ~2 years
ago)
What may happen is that at the time of irq injection there will be irq
with higher irr pending in APIC, But it looks like this already may
happen if injection failed on IDT access, but this is rare.
Right, we don't guarantee the precise time the APIC selects the vector
to inject, as long as it's after the last vmexit.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
