All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: "James H. Cloos Jr." <cloos@jhcloos.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	davej@suse.de
Subject: Re: new CPUID bit
Date: Wed, 15 Jan 2003 12:18:15 +0000	[thread overview]
Message-ID: <20030115121815.GB32694@codemonkey.org.uk> (raw)
In-Reply-To: <15909.7444.490945.972037@harpo.it.uu.se>

On Wed, Jan 15, 2003 at 09:34:28AM +0100, Mikael Pettersson wrote:

 > 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].

Or we change it so we end up with something like..

x86_capability[0].standard and x86_capability[0].extended

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

      reply	other threads:[~2003-01-15 12:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14 10:02 new CPUID bit Ulrich Drepper
2003-01-14 18:41 ` James H. Cloos Jr.
2003-01-15  8:34   ` Mikael Pettersson
2003-01-15 12:18     ` Dave Jones [this message]

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=20030115121815.GB32694@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=cloos@jhcloos.com \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.