From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Brian Gerst <brgerst@gmail.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Execute WP test after interrupts are enabled
Date: Tue, 25 Aug 2009 12:53:21 -0700 [thread overview]
Message-ID: <4A944131.90908@goop.org> (raw)
In-Reply-To: <73c1f2160908251237i3d32b39eu8e198e56610d5724@mail.gmail.com>
On 08/25/09 12:37, Brian Gerst wrote:
> Is there any reason to run this test at all on Xen? It's only needed
> for real 386 and some broken 486 processors.
>
Yeah. We could easily set boot_cpu_data.wp_works_ok and bypass the
test, but I think its highlighting some other bug.
J
prev parent reply other threads:[~2009-08-25 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 19:16 [PATCH] x86: Execute WP test after interrupts are enabled Pekka Enberg
2009-08-25 19:34 ` Jeremy Fitzhardinge
2009-08-25 19:38 ` Pekka Enberg
2009-08-25 19:53 ` Jeremy Fitzhardinge
2009-08-25 19:58 ` Pekka Enberg
2009-08-25 20:03 ` Ingo Molnar
2009-08-25 20:03 ` Arnd Hannemann
2009-08-25 19:37 ` Brian Gerst
2009-08-25 19:53 ` Jeremy Fitzhardinge [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=4A944131.90908@goop.org \
--to=jeremy@goop.org \
--cc=brgerst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
/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