WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH 17 of 20] VM exit handler of n2-guest
From: "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Date: Fri, 3 Jun 2011 16:06:53 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Delivery-date: Fri, 03 Jun 2011 01:08:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110602145953.GN5098@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <patchbomb.1307005033@xxxxxxxxxxxxxxxxxxxx> <24d4d7d3e4c44c8dc61f.1307005050@xxxxxxxxxxxxxxxxxxxx> <20110602145953.GN5098@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcwhNdPQWI6wFATQRIaB6uSVNgio/AAjytcA
Thread-topic: [Xen-devel] [PATCH 17 of 20] VM exit handler of n2-guest
> 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.

Thx, Eddie

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

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