From: Jeff Golds <jgolds@resilience.com>
To: Dave Jones <davej@suse.de>
Cc: Stefan Smietanowski <stesmi@stesmi.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] AMD SMP capability sanity checking.
Date: Fri, 16 Nov 2001 14:37:34 -0800 [thread overview]
Message-ID: <3BF5952E.E73BB648@resilience.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0111162302160.22827-100000@Appserv.suse.de>
Dave Jones wrote:
>
> On Fri, 16 Nov 2001, Stefan Smietanowski wrote:
>
> > 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.
>
> 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
>
> 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.
>
So the MP has the SMP capable bit set and the XP does not?
If so, I'm not convinced this is the correct way to approach this
issue. My reasoning is based on the fact that AMD is not exactly a
impartial source of information. AMD wants to sell more MP chips, so
they can say that only MP chips are SMP capable even if XP chips work
just fine.
Now, with your patch, if people successfully use XP chips in an SMP
configuration, you're giving the maintainers of the Linux kernel the
opportunity to ignore oopses reported from these people and I think
that's a bad thing. If someone can show that XPs are truly not SMP
capable, then, by all means, implement your patch as written.
The way I'd prefer to see this handled is that things are assumed to
work until proven otherwise. Sort of like the SMP Celeron systems
people have been using: Is there _any_ reason to believe that Celeron's
can't do SMP? Sure doesn't seem like it except for Intel's statement
that Celerons aren't SMP capable. And if you decide to taint oopses
from people with such configurations, I think you'll be doing the Linux
community a disservice.
-Jeff
P.S. BTW, I don't know all the Athlon steppings, but it sure looks like
_a lot_ of older Athlons/Durons are SMP capable. Does it seem likely
that this suddenly changed when AMD stamped XP or MP on the chip?
--
Jeff Golds
Sr. Software Engineer
jgolds@resilience.com
next prev parent reply other threads:[~2001-11-16 22:35 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 [this message]
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
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=3BF5952E.E73BB648@resilience.com \
--to=jgolds@resilience.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stesmi@stesmi.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