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

[Xen-devel] Re: One potential issue of shadow fault emulation

To: Tim Deegan <Tim.Deegan@xxxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Subject: [Xen-devel] Re: One potential issue of shadow fault emulation
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 21 Dec 2007 21:54:19 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 21 Dec 2007 13:55:14 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071221172142.GB4805@xxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AchEHAmLR/Omz7APEdy+BwAX8io7RQ==
Thread-topic: One potential issue of shadow fault emulation
User-agent: Microsoft-Entourage/11.3.6.070618
On 21/12/07 17:21, "Tim Deegan" <Tim.Deegan@xxxxxxxxxx> wrote:

> I think it's cleanest to just fail the emulation if we find we're
> writing to the vlapic, rather than adding special-case code to detect
> and handle TPR writes within the page.  Unless this is a particularly
> common path and would have a measurable performance impact for the extra
> VMEXIT.

Probably gfn_to_mfn() should explicitly check for vmx_apic_access_mfn and
return INVALID_MFN instead. That will fix all emulation routines by causing
them to take their mmio path (or bail if they don't have them) which is the
correct behaviour for this case.

This is certainly important enough to fix for 3.2.0 (and 3.1.3).

 -- Keir



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