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

Re: [Xen-devel] [PATCH][HVM] fix migration from NX-capable machine to non-NX-capable machine


  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
  • From: "Dave Lively" <dlively@xxxxxxxxxxxxxxx>
  • Date: Fri, 28 Sep 2007 09:22:34 -0400
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 28 Sep 2007 06:23:13 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=gWTM31dzqA8cDuvCTdbRvyn98kIct75Y4IpYrPQW3Az7lz4VzS3jJCJsCx9Jt5gsJqvHC2h6C+cgbHvBvWjKVukSdiz08Q0xBjZo3goqBAQOqULHu0eGcqYPf1hKO4U4nrAZ5Z8+AriWMZFHcC3KRxx8jrjFxzs9GauBqWG98Xk=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 9/28/07, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
> On 27/9/07 22:12, "David Lively" <dlively@xxxxxxxxxxxxxxx> wrote:
> > +    u64 efer_mask = EFER_SCE || (cpu_has_nx ? EFER_NX : 0);
>
> Wrong kind of OR?

Ack.  Yes, thank you.  It was "working" because EFER_SCE == 1, so
efer_mask was always 1, but this meant I was never propagating EFER_NX
....  I'll retest with '|' and get back to you.

> As for AMD, are there any SVM CPUs that do not also support NX?

I saw this bug on an Intel CPU that supported NX -- it was just
disabled in the BIOS.  I'll be speaking with some AMD folks later this
morning, so I'll ask whether the same thing is possible w/AMD SVM.

Dave

_______________________________________________
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®.