This patch adds correct handling of IDT_VECTORING_INFO_FIELD for the nested
case.
When a guest exits while delivering an interrupt or exception, we get this
information in IDT_VECTORING_INFO_FIELD in the VMCS. When L2 exits to L1,
there's nothing we need to do, because L1 will see this field in vm
This patch adds correct handling of IDT_VECTORING_INFO_FIELD for the nested
case.
When a guest exits while delivering an interrupt or exception, we get this
information in IDT_VECTORING_INFO_FIELD in the VMCS. When L2 exits to L1,
there's nothing we need to do, because L1 will see this field in vm
> From: Nadav Har'El
> Sent: Tuesday, May 17, 2011 3:57 AM
>
> This patch adds correct handling of IDT_VECTORING_INFO_FIELD for the
> nested
> case.
>
> When a guest exits while delivering an interrupt or exception, we get this
> information in IDT_VECTORING_INFO_FIELD in the VMCS. When L2 exits
On Wed, May 25, 2011, Tian, Kevin wrote about "RE: [PATCH 25/31] nVMX: Correct
handling of idt vectoring info":
> Here got one question. How about L2 has interrupt exiting disabled? That way
You are right, this is a bug in my code. It's a known bug - listed on my
private bugzi
> From: Nadav Har'El
> Sent: Wednesday, May 25, 2011 6:14 PM
>
> On Wed, May 25, 2011, Tian, Kevin wrote about "RE: [PATCH 25/31] nVMX:
> Correct handling of idt vectoring info":
> > Here got one question. How about L2 has interrupt exiting disabled? That
>
