This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH 09/17] vmx: nest: interrupt

At 10:41 +0100 on 22 Apr (1271932881), Qing He wrote:
> +/*
> + * Nested virtualization interrupt handling:
> + *
> + *   When vcpu runs in nested context (L2), the event delivery from
> + *   L0 to L1 may be blocked by several reasons:
> + *       - virtual VMExit
> + *       - virtual VMEntry

I'm not sure I understand what the plan is here.  It looks like you
queue up a virtual vmentry or vmexit so that it happens just before the
real vmentry and then have to hold off interrupt injection because of
it.  I'm a little worried that we'll end up taking a virtual vmexit for
an interrupt, and then not injecting the interrupt.

Maybe you could outline the overall design of how interrupt delivery and
virtual vmenter/vmexit should work in nested VMX.  I suspect that I've
just misunderstood the code.



Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, XenServer Engineering
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>