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/
Home Products Support Community News


Re: [Xen-devel] Re: [Xen-changelog] Fix NX/XD enable on secondary CPUs.

To: Gerd Knorr <kraxel@xxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-changelog] Fix NX/XD enable on secondary CPUs.
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 13 Jul 2005 11:52:27 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 13 Jul 2005 10:46:56 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <87vf3fko1x.fsf@xxxxxxxxxxx>
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>
References: <E1DscXL-0000Y9-14@xxxxxxxxxxxxxxxxxxxxx> <87vf3fko1x.fsf@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Does EFER_NX need setting for 32-bit PAE?

We don't set it for *any* cpus in x86_32 builds, even cpu0...

 -- Keir

On 13 Jul 2005, at 11:17, Gerd Knorr wrote:

I think I have this problem with PAE as well.  Machine is SMP
(hyperthreaded).  PAE dom0 boots fine on CPU #0.  PAE domU is bound to
CPU #1 by default and boots to the login prompt as well, but only with
NX disabled (and network disabled, but that's another story ...).

With NX-enabled domU boot I get this ...

(XEN) (file=traps.c, line=872) Non-priv domain attempted RDMSR(c0000080,00000000,20100000). (XEN) (file=traps.c, line=864) Non-priv domain attempted WRMSR(c0000080,00000800,00000000).

... and the kernel crashes shortly later, I guess due to NX pte entry
without NX being enabled on CPU #1.  It crashes right after the first
set_fixmap call which creates a pte entry with NX set.

Xen-devel mailing list

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