* Re: [Xen-changelog] Fix NX/XD enable on secondary CPUs.
[not found] <E1DscXL-0000Y9-14@xenbits.xensource.com>
@ 2005-07-13 10:17 ` Gerd Knorr
2005-07-13 10:52 ` Keir Fraser
0 siblings, 1 reply; 3+ messages in thread
From: Gerd Knorr @ 2005-07-13 10:17 UTC (permalink / raw)
To: xen-devel
Xen patchbot -unstable <patchbot-unstable@lists.xensource.com> writes:
> Fix NX/XD enable on secondary CPUs.
> Signed-off-by: Keir Fraser <keir@xensource.com>
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 */
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Re: [Xen-changelog] Fix NX/XD enable on secondary CPUs.
2005-07-13 10:17 ` [Xen-changelog] Fix NX/XD enable on secondary CPUs Gerd Knorr
@ 2005-07-13 10:52 ` Keir Fraser
2005-07-13 11:14 ` Gerd Knorr
0 siblings, 1 reply; 3+ messages in thread
From: Keir Fraser @ 2005-07-13 10:52 UTC (permalink / raw)
To: Gerd Knorr; +Cc: xen-devel
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Re: [Xen-changelog] Fix NX/XD enable on secondary CPUs.
2005-07-13 10:52 ` Keir Fraser
@ 2005-07-13 11:14 ` Gerd Knorr
0 siblings, 0 replies; 3+ messages in thread
From: Gerd Knorr @ 2005-07-13 11:14 UTC (permalink / raw)
To: Keir Fraser; +Cc: xen-devel
On Wed, Jul 13, 2005 at 11:52:27AM +0100, Keir Fraser wrote:
>
> Does EFER_NX need setting for 32-bit PAE?
>
> We don't set it for *any* cpus in x86_32 builds, even cpu0...
The Dom0 linux kernel probably does for CPU #0 ...
> > (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).
... what the DomU kernel isn't allowed to do on CPU #1.
Gerd
--
panic("it works"); /* avoid being flooded with debug messages */
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-07-13 11:14 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <E1DscXL-0000Y9-14@xenbits.xensource.com>
2005-07-13 10:17 ` [Xen-changelog] Fix NX/XD enable on secondary CPUs Gerd Knorr
2005-07-13 10:52 ` Keir Fraser
2005-07-13 11:14 ` Gerd Knorr
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.