From: Stefan Smietanowski <stesmi@stesmi.com>
To: Dave Jones <davej@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] AMD SMP capability sanity checking.
Date: Sat, 17 Nov 2001 00:40:43 +0100 [thread overview]
Message-ID: <3BF5A3FB.9000106@stesmi.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0111162302160.22827-100000@Appserv.suse.de>
Hi Dave.
>>Would you mind writing what each of these actually is?
>>Athlon 661 doesn't tell me much, neither does Duron 671.
>>That's just an example, which is which?
>
> The numbers translate to the family/model/stepping fields
> of /proc/cpuinfo.
Yeah, I know. That was the easy bit.
> The only older models certified as safe for SMP are.
>
> Athlon model 6, stepping 0 CPUID = 660
> Athlon model 6, stepping 1 CPUID = 661
> Duron model 7, stepping 0 CPUID = 670
Ok, since you're misunderstanding me, where do I find out which is
which, ie CPUID 660 is an ... and CPUID 670 is an ...
Point me to some good place to find out and I'm happy.
I'll try looking on www.amd.com to see if I can find it myself :)
> The newer models..
> model 6 stepping 2 and above 662
> model 7 stepping 1 and above 671
>
> have a cpuid flag that must be compared to find out if they
> are capable or not. Note that these id's tally with XP's and MP's.
> The capability bit is the only way to distinguish between these models.
Right, all I'd need is a way to match these numbers to core names. :)
// Stefan
next prev parent reply other threads:[~2001-11-16 23:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 21:30 [PATCH] AMD SMP capability sanity checking Dave Jones
2001-11-16 19:42 ` Gérard Roudier
2001-11-16 21:41 ` Randy.Dunlap
2001-11-16 21:46 ` Dave Jones
2001-11-16 21:44 ` Dan Hollis
2001-11-16 22:02 ` Dave Jones
2001-11-16 21:46 ` Jeff Garzik
2001-11-16 21:59 ` Stefan Smietanowski
2001-11-16 22:11 ` Dave Jones
2001-11-16 22:37 ` Jeff Golds
2001-11-16 23:04 ` Dave Jones
2001-11-17 0:33 ` Jeff Golds
2001-11-17 0:39 ` Dave Jones
2001-11-17 0:59 ` Andreas Boman
2001-11-17 1:54 ` Mike Fedyk
2001-11-17 4:11 ` Nathan Walp
2001-11-17 4:59 ` Mark Orr
2001-11-16 23:40 ` Stefan Smietanowski [this message]
2001-11-16 23:47 ` Dave Jones
2001-11-17 1:05 ` Stefan Smietanowski
2001-11-17 1:09 ` Dan Hollis
2001-11-17 1:11 ` Dave Jones
2001-11-17 1:10 ` Dave Jones
2001-11-21 0:42 ` Pavel Machek
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=3BF5A3FB.9000106@stesmi.com \
--to=stesmi@stesmi.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.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