From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Christoph Egger" Subject: Re: [PATCH][HVM] fix migration from NX-capable machine to non-NX-capable machine Date: Fri, 28 Sep 2007 15:32:51 +0200 Message-ID: <200709281532.52254.Christoph.Egger@amd.com> References: <46FC1CD4.6030905@virtualiron.com> <1b64e7ec0709280622m37f0c272y6b61a0f2ed92b210@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1b64e7ec0709280622m37f0c272y6b61a0f2ed92b210@mail.gmail.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com Cc: Dave Lively List-Id: xen-devel@lists.xenproject.org > > > 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. You can figure out, if NX is supported by looking up the EFER. It is possible to enable/disable NX in the PAE-paging mode by setting/clearing the NXE bit in EFER. Christoph =2D-=20 AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxony Limited Liability Company & Co. KG Sitz (Gesch=E4ftsanschrift): Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland Registergericht Dresden: HRA 4896 vertretungsberechtigter Komplement=E4r: AMD Saxony LLC (Sitz Wilmington, Delaware, USA) Gesch=E4ftsf=FChrer der AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy