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: Brian Gerst <bgerst@didntduck.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Fwd: CPU detection revamp (Request for comments)]
Date: Fri, 10 Nov 2000 11:55:03 -0800	[thread overview]
Message-ID: <3A0C5297.D039881@transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011101937510.552-100000@neo.local>

davej@suse.de wrote:

> On Fri, 10 Nov 2000, Brian Gerst wrote:
> 
> > > features        : fpu vme de pse tsc msr mce cx8 pge mmx syscall 3dnow
> >
> > The K6's don't support sysenter/sysexit.
> 
> The K6 datasheets suggests otherwise.
> Some models seem to have sysenter/sysexit, whilst others have
> syscall/sysret. No model seems to have both.

Athlons have both.  Since the ext-bit 10 stuff is useless, I haven't
bothered reporting it at all.

> The datasheets are somewhat confusing, as it doesn't mention bit 10
> at all, just an oversized box for bit 11.
> 
> > It really should have been marked differently before.
> 
> Before we weren't mentioning it at all, look..
> flags  : fpu vme de pse tsc msr mce cx8 sep mtrr pge mmx 3dnow
> 
> > 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.
> 
> And where does sysenter/sysexit fit in?

sysenter/sysexit is the "sep" feature.

	-hpa

-- 
<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 19:55 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
2000-11-10 19:49     ` davej
2000-11-10 19:55       ` H. Peter Anvin [this message]
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=3A0C5297.D039881@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=bgerst@didntduck.org \
    --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