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] AMD-V not functional starting with c/s 11132

To: "Woller, Thomas" <thomas.woller@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] AMD-V not functional starting with c/s 11132
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 17 Aug 2006 19:27:02 +0100
Delivery-date: Thu, 17 Aug 2006 11:27:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <683860AD674C7348A0BF0DE3918482F6029B10FF@xxxxxxxxxxxxxxxxx>
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: AcbCH4hTJYUeUNTZRpWFX1NDLvPqFAACzNeZ
Thread-topic: [Xen-devel] AMD-V not functional starting with c/s 11132
User-agent: Microsoft-Entourage/11.2.5.060620
On 17/8/06 6:06 pm, "Woller, Thomas" <thomas.woller@xxxxxxx> wrote:

> AMD-V (aka SVM) is broken for 64bit hv (can not start any guests), we've
> traced it down to c/s 11132 (clean up of HVM). we are working to
> understand the patch, and provide fixes for the svm code path.  Looks
> like 32bit code path needs a bit of attention also, but is booting. If
> you want to use AMD-V please use c/s 11131 or earlier.
> Tom

This is a bug in the changes that patch made to x86_64/exits.S, which
changed the way we compute the address for host VMLOAD/VMSAVE. We end up
with the address of the location that contains the VMCB pointer, rather than
the VMCB pointer itself! Try adding 'mov (%rax),%rax' immediately before the
host VMLOAD/VMSAVE instructions.

I've fixed this in xen-unstable hopefully, changeset 11184, which will be in
the public tree when we have fixed another issue ion our staging tree.

 -- Keir



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

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