[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 6/7, RFC] x86_64: basic changes for supporting compatibility mode guest


  • To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • 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
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcbGn6Iz4OLmJTKSEduhlQAKle7CWA==
  • Thread-topic: [Xen-devel] [PATCH 6/7, RFC] x86_64: basic changes for supporting compatibility mode guest



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.