All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@suse.de>
To: xen-devel@lists.xensource.com
Subject: Re: [Xen-changelog] Fix NX/XD enable on secondary CPUs.
Date: 13 Jul 2005 12:17:30 +0200	[thread overview]
Message-ID: <87vf3fko1x.fsf@bytesex.org> (raw)
In-Reply-To: <E1DscXL-0000Y9-14@xenbits.xensource.com>

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 */

       reply	other threads:[~2005-07-13 10:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1DscXL-0000Y9-14@xenbits.xensource.com>
2005-07-13 10:17 ` Gerd Knorr [this message]
2005-07-13 10:52   ` Re: [Xen-changelog] Fix NX/XD enable on secondary CPUs Keir Fraser
2005-07-13 11:14     ` Gerd Knorr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vf3fko1x.fsf@bytesex.org \
    --to=kraxel@suse.de \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.