From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"x86 maintainers" <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] x86 fixes (NOPL issue)
Date: Fri, 5 Sep 2008 20:01:16 -0700 [thread overview]
Message-ID: <86802c440809052001o71892669ofe42ee4772654eeb@mail.gmail.com> (raw)
In-Reply-To: <200809060222.m862MVtP024813@askone.hos.anvin.org>
On Fri, Sep 5, 2008 at 7:22 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> Hi Linus,
>
> Please pull:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git x86-fixes-for-linus-2
>
> H. Peter Anvin (4):
> x86: boot: stub out unimplemented CPU feature words
diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
> index 80ab20d..0785b3c 100644
> --- a/arch/x86/kernel/cpu/common.c
> +++ b/arch/x86/kernel/cpu/common.c
> @@ -13,6 +13,7 @@
> #include <asm/mtrr.h>
> #include <asm/mce.h>
> #include <asm/pat.h>
> +#include <asm/asm.h>
> #ifdef CONFIG_X86_LOCAL_APIC
> #include <asm/mpspec.h>
> #include <asm/apic.h>
> @@ -341,6 +342,35 @@ static void __init early_cpu_detect(void)
> early_get_cap(c);
> }
>
> +/*
> + * The NOPL instruction is supposed to exist on all CPUs with
> + * family >= 6, unfortunately, that's not true in practice because
> + * of early VIA chips and (more importantly) broken virtualizers that
> + * are not easy to detect. Hence, probe for it based on first
> + * principles.
> + */
if so, should only test on VIA chips.
YH
next prev parent reply other threads:[~2008-09-06 3:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-06 2:22 [git pull] x86 fixes (NOPL issue) H. Peter Anvin
2008-09-06 3:01 ` Yinghai Lu [this message]
2008-09-08 15:02 ` David Sanders
[not found] <fa.HDZlnwhQIaOU7WkvenWvWDveLiI@ifi.uio.no>
[not found] ` <fa.uHa5kqSRJ8gj0H3r9BmGsTqRvFI@ifi.uio.no>
2008-09-06 4:03 ` Robert Hancock
2008-09-06 4:07 ` H. Peter Anvin
2008-09-06 5:50 ` Yinghai Lu
2008-09-06 5:53 ` H. Peter Anvin
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=86802c440809052001o71892669ofe42ee4772654eeb@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox