From: Jeff Garzik <jgarzik@pobox.com>
To: pluto@pld-linux.org, akpm@osdl.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ix86,x86_64 cpu features
Date: Tue, 24 Aug 2004 20:47:35 -0400 [thread overview]
Message-ID: <412BE1A7.1080407@pobox.com> (raw)
In-Reply-To: <200408242233.i7OMXrTd001684@hera.kernel.org>
Linux Kernel Mailing List wrote:
> diff -Nru a/include/asm-x86_64/cpufeature.h b/include/asm-x86_64/cpufeature.h
> --- a/include/asm-x86_64/cpufeature.h 2004-08-24 15:34:02 -07:00
> +++ b/include/asm-x86_64/cpufeature.h 2004-08-24 15:34:02 -07:00
> @@ -63,8 +63,14 @@
> #define X86_FEATURE_K8_C (3*32+ 4) /* C stepping K8 */
>
> /* Intel-defined CPU features, CPUID level 0x00000001 (ecx), word 4 */
> -#define X86_FEATURE_EST (4*32+ 7) /* Enhanced SpeedStep */
> +#define X86_FEATURE_XMM3 (4*32+ 0) /* Streaming SIMD Extensions-3 */
> #define X86_FEATURE_MWAIT (4*32+ 3) /* Monitor/Mwait support */
> +#define X86_FEATURE_DSCPL (4*32+ 4) /* CPL Qualified Debug Store */
> +#define X86_FEATURE_EST (4*32+ 7) /* Enhanced SpeedStep */
> +#define X86_FEATURE_TM2 (4*32+ 8) /* Thermal Monitor 2 */
> +#define X86_FEATURE_CID (4*32+10) /* Context ID */
> +#define X86_FEATURE_CX16 (4*32+13) /* CMPXCHG16B */
> +#define X86_FEATURE_XTPR (4*32+14) /* Send Task Priority Messages */
FYI, the style for cpufeature.h is to _not_ add constants for a feature
bit unless that feature is actually used.
Jeff, one of the people who last touched this area of code
next parent reply other threads:[~2004-08-25 0:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200408242233.i7OMXrTd001684@hera.kernel.org>
2004-08-25 0:47 ` Jeff Garzik [this message]
[not found] <2sMat-61I-43@gated-at.bofh.it>
2004-08-13 16:11 ` [PATCH] [ix86,x86_64] cpu features Andi Kleen
2004-08-13 17:02 ` Paweł Sikora
2004-08-13 17:08 ` Paweł Sikora
2004-08-13 20:14 ` Andi Kleen
2004-08-13 20:29 ` Paweł Sikora
2004-08-13 15:24 Paweł Sikora
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=412BE1A7.1080407@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pluto@pld-linux.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 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.