public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: davej@suse.de
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Fwd: CPU detection revamp (Request for comments)]
Date: Fri, 10 Nov 2000 10:20:47 -0800	[thread overview]
Message-ID: <3A0C3C7F.FF594CE9@transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011101751080.514-100000@neo.local>

davej@suse.de wrote:
> 
> Hi hpa,
> 
>  First test, the AMD K6-2.
> 
> Before your patch..
>         cpu family      : 5
>         model           : 8
>         stepping        : 12
> 
> After..
> 
>         cpu family      : 5
>         model           : 8
>         stepping        : 4
> 
> Line 1826 of setup.c
> 
>         c->x86_mask = tfms & 7;
> 
> Should be..
> 
>         c->x86_mask = tfms & 15;
> 
> I think?
> 
> Also, look at the feature flags:
> before:
> flags           : fpu vme de pse tsc msr mce cx8 sep mtrr pge mmx 3dnow
> 
> after:
> features        : fpu vme de pse tsc msr mce cx8 pge mmx syscall 3dnow
> 
> Note, I lost MTRR & sep. This may be related to the stepping bug
> though. I'll recompile a kernel with the &15 fix, and see if that cures
> all.
> 

That is actually correct -- the K6-2 doesn't actually have mtrr and sep,
but has syscall and k6_mtrr instead (the stepping bug causes k6_mtrr not
to show up.)  Part of the bugginess of the old system was using one flag
for multiple purposes.  This was Linux' doing, not AMD's, by the way.

> btw, whilst all this is getting a shakedown, how about renaming
> that 'x86_mask' field to the more obvious 'x86_stepping' ?
> c->x86 would make more sense as c->x86_family too thinking about it.
> 

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-10 18:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3A0B6B43.D1210AAA@transmeta.com>
2000-11-10 17:56 ` [Fwd: CPU detection revamp (Request for comments)] davej
2000-11-10 18:20   ` H. Peter Anvin [this message]
2000-11-10 19:51     ` davej
2000-11-10 18:50   ` Brian Gerst
2000-11-10 19:49     ` davej
2000-11-10 19:55       ` H. Peter Anvin
2000-11-10 20:26         ` davej
2000-11-10 20:33       ` Brian Gerst
2000-11-10 23:06         ` davej

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=3A0C3C7F.FF594CE9@transmeta.com \
    --to=hpa@transmeta.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