From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux@sandersweb.net, linux-kernel@vger.kernel.org,
the arch/x86 maintainers <x86@kernel.org>,
Andi Kleen <andi-suse@firstfloor.org>
Subject: Re: [BUG] x86 kenel won't boot under Virtual PC
Date: Mon, 08 Sep 2008 08:36:48 -0700 [thread overview]
Message-ID: <48C54690.1060002@zytor.com> (raw)
In-Reply-To: <20080908152330.GA9784@elte.hu>
Ingo Molnar wrote:
>
> yes. X86_P6_NOPS is a totally insignificant optimization and if it makes
> _any_ CPU not boot (be that virtual or real), then it's frankly not
> worth it.
>
> David, exactly how does the kernel fail to boot with latest -git?
> (v2.6.27-rc5-313-g64f996f or later) Does detect_nopl() run? It really
> should, and it should detect the non-working instructions.
>
Okay, a few things here...
1. First, I wrote up a patch yesterday to update the CONFIG_X86_GENERIC
description and to make it "default y". It is currently on
x86/defconfig, but I think it should be promoted to mainline immediately.
2. X86_P6_NOPS is not the only source of static NOPLs. If gcc is set to
optimize for specific architectures, then gcc/binutils will generate
static NOPLs. The only way we can prevent that is by not using specific
-march options, as far as I can tell.
3. I'm not positive that CONFIG_X86_GENERIC currently avoid all cases of
(2), but it obviously should. I will verify that today and add a
followup patch to the Makefiles if necessary.
Given all of this, I really think that putting this on
CONFIG_X86_GENERIC, *AND* making CONFIG_X86_GENERIC the default is the
right choice.
-hpa
next prev parent reply other threads:[~2008-09-08 15:38 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-31 18:22 [BUG] x86 kenel won't boot under Virtual PC David Sanders
2008-08-31 18:47 ` Linus Torvalds
2008-08-31 19:27 ` Arjan van de Ven
2008-08-31 19:39 ` Linus Torvalds
2008-09-05 15:38 ` David Sanders
2008-09-05 16:15 ` Jan Beulich
2008-09-05 16:39 ` Linus Torvalds
2008-09-05 18:43 ` Ingo Molnar
2008-09-05 20:06 ` H. Peter Anvin
2008-09-05 19:08 ` Jeremy Fitzhardinge
2008-09-05 20:12 ` H. Peter Anvin
2008-09-05 16:30 ` Linus Torvalds
2008-09-05 17:55 ` Andi Kleen
2008-08-31 20:03 ` David Sanders
2008-09-01 20:23 ` David Sanders
2008-09-01 22:22 ` Linus Torvalds
2008-09-02 12:08 ` David Sanders
2008-09-02 18:12 ` Linus Torvalds
2008-09-02 18:44 ` David Sanders
2008-09-03 11:09 ` Peter Zijlstra
2008-09-03 11:20 ` David Sanders
[not found] ` <48C1C156.9080003@zytor.com>
2008-09-07 20:07 ` David Sanders
2008-09-07 23:22 ` David Sanders
2008-09-08 1:48 ` H. Peter Anvin
2008-09-08 2:49 ` David Sanders
2008-09-08 4:04 ` H. Peter Anvin
2008-09-08 9:42 ` Andi Kleen
2008-09-08 13:25 ` David Sanders
2008-09-08 15:09 ` Linus Torvalds
2008-09-08 15:23 ` Ingo Molnar
2008-09-08 15:36 ` H. Peter Anvin [this message]
2008-09-08 15:38 ` David Sanders
2008-09-08 15:38 ` H. Peter Anvin
2008-09-08 15:45 ` Andi Kleen
2008-09-08 15:43 ` H. Peter Anvin
2008-09-08 15:50 ` H. Peter Anvin
2008-09-08 15:50 ` Andi Kleen
2008-09-08 15:50 ` H. Peter Anvin
2008-09-08 15:57 ` Andi Kleen
2008-09-08 15:54 ` H. Peter Anvin
2008-09-08 16:07 ` Linus Torvalds
2008-09-08 16:13 ` H. Peter Anvin
2008-09-08 16:15 ` H. Peter Anvin
2008-09-08 16:26 ` David Sanders
2008-09-08 16:20 ` Linus Torvalds
2008-09-08 16:32 ` H. Peter Anvin
2008-09-08 17:02 ` Ingo Molnar
2008-09-08 16:34 ` david
2008-09-08 16:42 ` H. Peter Anvin
2008-09-08 18:51 ` david
2008-09-08 16:59 ` Linus Torvalds
2008-09-08 17:00 ` Andi Kleen
2008-09-08 17:04 ` Linus Torvalds
2008-09-08 17:08 ` H. Peter Anvin
2008-09-08 17:12 ` H. Peter Anvin
2008-09-08 17:41 ` Linus Torvalds
2008-09-08 17:38 ` Linus Torvalds
2008-09-08 17:59 ` H. Peter Anvin
2008-09-08 19:09 ` H. Peter Anvin
2008-09-08 22:42 ` Linus Torvalds
2008-09-08 17:18 ` Andi Kleen
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=48C54690.1060002@zytor.com \
--to=hpa@zytor.com \
--cc=andi-suse@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@sandersweb.net \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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.