From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Deegan Subject: Re: [PATCH 17 of 20] VM exit handler of n2-guest Date: Thu, 2 Jun 2011 15:59:53 +0100 Message-ID: <20110602145953.GN5098@whitby.uk.xensource.com> References: <24d4d7d3e4c44c8dc61f.1307005050@nest-wsm.los-vmm.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Return-path: Content-Disposition: inline In-Reply-To: <24d4d7d3e4c44c8dc61f.1307005050@nest-wsm.los-vmm.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Eddie Dong Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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. Cheers, Tim. -- Tim Deegan Principal Software Engineer, Xen Platform Team Citrix Systems UK Ltd. (Company #02937203, SL9 0BG)