[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.