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 6/7, RFC] x86_64: basic changes for supporting co

To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 6/7, RFC] x86_64: basic changes for supporting compatibility mode guest
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 23 Aug 2006 11:33:55 +0100
Delivery-date: Wed, 23 Aug 2006 03:34:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <44EC4ACC.76E4.0078.0@xxxxxxxxxx>
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: AcbGn6Iz4OLmJTKSEduhlQAKle7CWA==
Thread-topic: [Xen-devel] [PATCH 6/7, RFC] x86_64: basic changes for supporting compatibility mode guest
User-agent: Microsoft-Entourage/11.2.5.060620


On 23/8/06 11:32 am, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> There was one more issue I forgot to mention: We must disable execution of
> 'syscall' in some way for compatibility domains. The question is whether to
> add respective detection code early into the syscall path (which would affect
> performance-wise all 64-bit domains) or whether to {dis,en}able the use of
> the instruction in the context switch code by updating EFER as needed
> (which would have a performance effect only when switching between
> a native and a compatibility domain, but the performance effect would likely
> be significantly greater). I'd prefer the second option, not the least because
> its implementation is significantly easier.

I'm not fussed either way really. It depends how slow it is to update EFER.
That'd be easy to check.

 -- Keir



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