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

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


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Gerd Knorr <kraxel@xxxxxxx>
  • Date: 13 Jul 2005 12:17:30 +0200
  • Delivery-date: Wed, 13 Jul 2005 10:18:45 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Xen patchbot -unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx> writes:

> Fix NX/XD enable on secondary CPUs.
> Signed-off-by: Keir Fraser <keir@xxxxxxxxxxxxx>

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.

  Gerd

-- 
panic("it works"); /* avoid being flooded with debug messages */

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