From: Mikael Pettersson <mikpe@csd.uu.se>
To: "James H. Cloos Jr." <cloos@jhcloos.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, davej@suse.de
Subject: Re: new CPUID bit
Date: Wed, 15 Jan 2003 09:34:28 +0100 [thread overview]
Message-ID: <15909.7444.490945.972037@harpo.it.uu.se> (raw)
In-Reply-To: <m38yxn377m.fsf@lugabout.jhcloos.org>
James H. Cloos Jr. writes:
> Ulrich> Northwood P4's have one more bit in the CPUID processor info
> Ulrich> set: bit 31. Intel calls the feature PBE (Pending Break
> Ulrich> Enable).
>
> For the curious, from <http://www.aceshardware.com/forum?read=80030620>:
>
> Adrian> Bit 31 is PBE (Pending Break Enable) which you can find in the
> Adrian> latest P4 instruction manual (document 24547106, page
> Adrian> 159-162). To quote:
A better reference for this stuff is (IMHO) AP-485, the "Intel Processor
Identification and the CPUID Instruction" application note. It's regularly
updated, and in this particular case, its description of CPUID with EAX=1
differs from the IA32 Volume 2 manual (245471xx) in two ways:
- EBX bit 31 is called "SBF", Signal Break on FERR.
- ECX is defined to contain additional feature flags. Currently only one
is defined: ECX bit 10 is the "Context ID" feature for putting the L1
D-cache in adaptive or shared mode, which matters for hyper-threaded CPUs.
Supporting the new ECX feature flags in the kernel will require some surgery,
since the current code assumes x86_capability[0] is Intel, [1] is AMD,
[2] is Transmeta, and [3] is for conflicting or synthesized feature flags.
We either shift AMD etc down one index and put ECX in [1], or add a new index
[4] for ECX, or kludge the few ECX-defined features in [3].
/Mikael
next prev parent reply other threads:[~2003-01-15 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 10:02 Ulrich Drepper
2003-01-14 18:41 ` James H. Cloos Jr.
2003-01-15 8:34 ` Mikael Pettersson [this message]
2003-01-15 12:18 ` Dave Jones
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=15909.7444.490945.972037@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=cloos@jhcloos.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
all inboxes | Powered by JetHome®