Re: [Xen-devel] [PATCH 17 of 20] VM exit handler of n2-guest

[Tim Deegan <Tim.Deegan@xxxxxxxxxx>]

At 16:06 +0800 on 03 Jun (1307117213), Dong, Eddie wrote:
> > At 16:57 +0800 on 02 Jun (1307033850), Eddie Dong wrote:
> > > +    case EXIT_REASON_WBINVD:
> > > +    case EXIT_REASON_EPT_VIOLATION:
> > > +    case EXIT_REASON_EPT_MISCONFIG:
> > > +    case EXIT_REASON_EXTERNAL_INTERRUPT:
> > > +        /* pass to L0 handler */
> > > +        break;
> > 
> > If the L1 guest asked to intercept WBINVD, will it ever get the VMEXIT?
> > I didn't see any code in the L0 WBINVD handler to pass it on.
> > 

> Current patch doesn't expose Secondary Processor-Based VM-Execution
> Controls. So WBINVD exiting capability is removed in L1 guest.

Ah, OK, thanks. 

Tim.

-- 
Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, Xen Platform Team
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel