From: Keir Fraser <keir.xen@gmail.com>
To: "Li, Xin" <xin.li@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: [PATCH] CPUID level 0x00000007:0 (ebx) is word 9, instead of word 7
Date: Tue, 31 May 2011 13:39:34 +0100 [thread overview]
Message-ID: <CA0AA016.1B4F6%keir.xen@gmail.com> (raw)
In-Reply-To: <FC2FB65B4D919844ADE4BE3C2BB739AD5AA820E8@shsmsx501.ccr.corp.intel.com>
On 31/05/2011 00:39, "Li, Xin" <xin.li@intel.com> wrote:
> CPUID level 0x00000007:0 (ebx) is word 9, instead of word 7.
>
> ... make it consistent with native Linux.
This is just a cleanup, not a bug fix?
-- Keir
> Signed-off-by: Li Xin <xin.li@intel.com>
>
> diff -r d7c755c25bb9 xen/include/asm-x86/cpufeature.h
> --- a/xen/include/asm-x86/cpufeature.h Sat May 28 08:58:08 2011 +0100
> +++ b/xen/include/asm-x86/cpufeature.h Tue May 31 07:34:34 2011 +0800
> @@ -142,7 +142,7 @@
> #define X86_FEATURE_TOPOEXT (6*32+22) /* topology extensions CPUID leafs
> */
>
> /* Intel-defined CPU features, CPUID level 0x00000007:0 (ebx), word 9 */
> -#define X86_FEATURE_FSGSBASE (7*32+ 0) /* {RD,WR}{FS,GS}BASE instructions
> */
> +#define X86_FEATURE_FSGSBASE (9*32+ 0) /* {RD,WR}{FS,GS}BASE instructions
> */
>
> #define cpu_has(c, bit) test_bit(bit, (c)->x86_capability)
> #define boot_cpu_has(bit) test_bit(bit, boot_cpu_data.x86_capability)
next prev parent reply other threads:[~2011-05-31 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 23:39 [PATCH] CPUID level 0x00000007:0 (ebx) is word 9, instead of word 7 Li, Xin
2011-05-31 12:39 ` Keir Fraser [this message]
2011-05-31 12:54 ` Jan Beulich
2011-05-31 14:59 ` Li, Xin
2011-06-01 6:35 ` Jan Beulich
2011-06-01 6:47 ` Keir Fraser
2011-06-01 14:41 ` Li, Xin
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=CA0AA016.1B4F6%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
--cc=xin.li@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).