From: Brian Gerst <bgerst@didntduck.org>
To: davej@suse.de
Cc: "H. Peter Anvin" <hpa@transmeta.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Fwd: CPU detection revamp (Request for comments)]
Date: Fri, 10 Nov 2000 13:50:04 -0500 [thread overview]
Message-ID: <3A0C435C.A31A38EC@didntduck.org> (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.
>
> 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.
The K6's don't support sysenter/sysexit. It really should have been
marked differently before. The early K6's used extended bit 10 to
indicate syscall/sysret capabality, but this version has some quirks
that make it pretty much unusable. Later K6's use extended bit 11 to
indicate syscall/sysret.
--
Brian Gerst
-
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/
next prev parent reply other threads:[~2000-11-10 18:52 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
2000-11-10 19:51 ` davej
2000-11-10 18:50 ` Brian Gerst [this message]
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=3A0C435C.A31A38EC@didntduck.org \
--to=bgerst@didntduck.org \
--cc=davej@suse.de \
--cc=hpa@transmeta.com \
--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