From: "H. Peter Anvin" <hpa@zytor.com>
To: Yuhong Bao <yuhongbao_386@hotmail.com>,
"mingo@kernel.org" <mingo@kernel.org>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"fernando@oss.ntt.co.jp" <fernando@oss.ntt.co.jp>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"hpa@linux.intel.com" <hpa@linux.intel.com>
Subject: RE: [tip:x86/urgent] x86-64, init: Do not set NX bits on non-NX capable hardware
Date: Sat, 11 May 2013 07:55:58 -0700 [thread overview]
Message-ID: <6d735c4c-ee73-4f42-baa9-1791bae17ed6@email.android.com> (raw)
In-Reply-To: <BLU177-W369899F15977E6D1D880C0C3A60@phx.gbl>
Yes... But both apply.
Yuhong Bao <yuhongbao_386@hotmail.com> wrote:
>(resending as plaintext)
>> During early init, we would incorrectly set the NX bit even if the NX
>> feature was not supported. Instead, only set this bit if NX is
>> actually available and enabled. We already do very early detection
>of
>> the NX bit to enable it in EFER, this simply extends this detection
>to
>> the early page table mask.
>AFAIK the only production x86-64 processor that don't support NX that I
>know of is the original Nocona D0 stepping.
>Must more common are the problem of BIOSes disabling the NX feature.
>
>
>Yuhong Bao
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
prev parent reply other threads:[~2013-05-11 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 6:40 [PATCH] x86, 64bit: do not assume CPU is NX capable when setting early page tables Fernando Luis Vázquez Cao
2013-05-02 18:33 ` [tip:x86/urgent] x86-64, init: Do not set NX bits on non-NX capable hardware tip-bot for H. Peter Anvin
2013-05-11 5:57 ` Yuhong Bao
2013-05-11 14:55 ` H. Peter Anvin [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=6d735c4c-ee73-4f42-baa9-1791bae17ed6@email.android.com \
--to=hpa@zytor.com \
--cc=fernando@oss.ntt.co.jp \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=yuhongbao_386@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®