From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: linux-kernel@vger.kernel.org, ak@suse.de, akpm@osdl.org
Subject: Re: [Patch] x86, x86_64: fix cpu model for family 0x6
Date: Fri, 30 Sep 2005 15:09:46 +0200 [thread overview]
Message-ID: <433D391A.70607@vc.cvut.cz> (raw)
In-Reply-To: <20050929190419.C15943@unix-os.sc.intel.com>
Siddha, Suresh B wrote:
> Andi, please pickup this patch and push to Andrew/Linus.
>
> thanks,
> suresh
>
> --
> According to cpuid instruction in IA32 SDM-Vol2, when computing cpu model,
> we need to consider extended model ID for family 0x6 also.
>
> Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
>
> --- linux-2.6.14-rc2-git7/arch/i386/kernel/cpu/common.c~ 2005-09-29 17:44:12.030688920 -0700
> +++ linux-2.6.14-rc2-git7/arch/i386/kernel/cpu/common.c 2005-09-29 17:44:30.967810040 -0700
> @@ -233,10 +233,10 @@ static void __init early_cpu_detect(void
> cpuid(0x00000001, &tfms, &misc, &junk, &cap0);
> c->x86 = (tfms >> 8) & 15;
> c->x86_model = (tfms >> 4) & 15;
> - if (c->x86 == 0xf) {
> + if (c->x86 == 0xf)
> c->x86 += (tfms >> 20) & 0xff;
> + if (c->x86 == 0x6 || c->x86 == 0xf)
Are you sure this is correct? You just incremented c->x86 by extended
family, so I believe test should be
if (c->x86 == 0x6 || c->x86 >= 0xf)
or maybe just
if (c->x86 >= 0x6)
as chips with family 7..14 will either never appear, or they'll follow
existing rules (I believe all chips ever built return upper bits of tfms
zeroed, so maybe we could get rid of all these 'if' completely).
Petr Vandrovec
next prev parent reply other threads:[~2005-09-30 13:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 2:04 [Patch] x86, x86_64: fix cpu model for family 0x6 Siddha, Suresh B
2005-09-30 8:11 ` Andi Kleen
2005-09-30 13:09 ` Petr Vandrovec [this message]
2005-09-30 18:23 ` Siddha, Suresh B
2005-09-30 22:02 ` Andi Kleen
2005-09-30 22:23 ` Siddha, Suresh B
2005-09-30 22:37 ` Petr Vandrovec
2005-09-30 22:56 ` Dave Jones
2005-09-30 22:46 ` Andi Kleen
2005-10-01 1:37 ` Siddha, Suresh B
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=433D391A.70607@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suresh.b.siddha@intel.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