All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerone Young <jyoung5@us.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: xen-devel@lists.xensource.com, Jerone Young <jerone@gmail.com>
Subject: Re: Re: [PATCH] supporting non-NX/XD capable processors on x86_64 xenlinux
Date: Thu, 18 Aug 2005 11:24:52 -0500	[thread overview]
Message-ID: <1124382292.7723.11.camel@thinkpad> (raw)
In-Reply-To: <20050818161834.GB6977@wotan.suse.de>

On Thu, 2005-08-18 at 18:18 +0200, Andi Kleen wrote:
> On Thu, Aug 18, 2005 at 11:05:42AM -0500, Jerone Young wrote:
> > On Thu, 2005-08-18 at 17:51 +0200, Andi Kleen wrote:
> > > Keir Fraser <Keir.Fraser@cl.cam.ac.uk> writes:
> > > > 
> > > > By the way -- from what I've seen of this NX/XD discussion so far, it
> > > > sounds like even if CPUID says that NX/XD is supported, and you set
> > > > the EFER.NXE bit, the BIOS can still cause this to be ignored! Is this
> > > > true and, if so, what will happen if you try to use NX/XD anyway?
> > > > i.e., will the bit be ignored, or will its use cause a page fault?
> > > 
> > > I don't think that can happen. When NX is disabled or not there it
> > > doesn't appear in CPUID.
> > 
> > Ah but it does:

hehe... I didn't realize I left that statement in there...I just wanted
to post to the list to confirm with an example. Don't worry Andi ...
your still the x86-64 god in my book!

> 
> Your example confirms what I said.

> 
> -Andi
> 
-- 
Jerone Young
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)

      reply	other threads:[~2005-08-18 16:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-18 14:15 [PATCH] supporting non-NX/XD capable processors on x86_64 xenlinux Nakajima, Jun
2005-08-18 15:09 ` Keir Fraser
2005-08-18 15:39   ` Jerone Young
2005-08-18 16:05     ` Keir Fraser
2005-08-18 15:51   ` Andi Kleen
2005-08-18 16:05     ` Jerone Young
2005-08-18 16:18       ` Andi Kleen
2005-08-18 16:24         ` Jerone Young [this message]

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=1124382292.7723.11.camel@thinkpad \
    --to=jyoung5@us.ibm.com \
    --cc=ak@suse.de \
    --cc=jerone@gmail.com \
    --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.