From: Ingo Molnar <mingo@elte.hu>
To: Pekka Enberg <penberg@cs.helsinki.fi>, "H. Peter Anvin" <hpa@zytor.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
linux-kernel@vger.kernel.org,
Arnd Hannemann <hannemann@nets.rwth-aachen.de>,
Brian Gerst <brgerst@gmail.com>
Subject: Re: [PATCH] x86: Execute WP test after interrupts are enabled
Date: Tue, 25 Aug 2009 22:03:28 +0200 [thread overview]
Message-ID: <20090825200328.GA21677@elte.hu> (raw)
In-Reply-To: <84144f020908251258p71d5ad2fx7d31361c243a698e@mail.gmail.com>
* Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> On Tue, Aug 25, 2009 at 10:53 PM, Jeremy Fitzhardinge<jeremy@goop.org> wrote:
> > On 08/25/09 12:38, Pekka Enberg wrote:
> >> On Tue, 2009-08-25 at 12:34 -0700, Jeremy Fitzhardinge wrote:
> >>
> >>> I don't think this is the real fix, and it seems a bit ugly. ?I'm OK
> >>> with it as a workaround, but I think it will end up getting reverted if
> >>> applied.
> >>>
> >> Yeah, I'm fine with that. It's just that we're really late in the
> >> release cycle now so I'd like to keep the fix as simple as possible.
> >
> > Yeah, that's fine, but I think something like this would be simpler.
> > Arnd, could you test it please?
> >
> > From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> > Date: Tue, 25 Aug 2009 12:47:17 -0700
> > Subject: [PATCH] xen: suppress WP test
> >
> > Xen always runs on CPUs which properly support WP enforcement in
> > privileged mode, so there's no need to test for it.
> >
> > This also works around a crash reported by Arnd Hannemann, though
> > I think its just a band-aid for that case.
> >
> > Reported-by: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
> > Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> > Cc: Pekka Enberg <penberg@cs.helsinki.fi>
> >
> > diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
> > index 16d0d70..e5b903b 100644
> > --- a/arch/x86/xen/enlighten.c
> > +++ b/arch/x86/xen/enlighten.c
> > @@ -1069,6 +1069,7 @@ asmlinkage void __init xen_start_kernel(void)
> > ? ? ? ?/* set up basic CPUID stuff */
> > ? ? ? ?cpu_detect(&new_cpu_data);
> > ? ? ? ?new_cpu_data.hard_math = 1;
> > + ? ? ? new_cpu_data.wp_works_ok = 1;
> > ? ? ? ?new_cpu_data.x86_capability[0] = cpuid_edx(1);
> > ?#endif
>
> Yeah, this is even better assuming it works. :-)
>
> Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
yeah, we should do this one for .31.
Ingo
next prev parent reply other threads:[~2009-08-25 20:03 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 [this message]
2009-08-25 20:03 ` Arnd Hannemann
2009-08-25 19:37 ` Brian Gerst
2009-08-25 19:53 ` Jeremy Fitzhardinge
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=20090825200328.GA21677@elte.hu \
--to=mingo@elte.hu \
--cc=brgerst@gmail.com \
--cc=hannemann@nets.rwth-aachen.de \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--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