From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: the arch/x86 maintainers <x86@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Austin Zhang <austin_zhang@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Cleanup and updates of x86 CPU definitions
Date: Thu, 28 Aug 2008 13:22:36 -0700 [thread overview]
Message-ID: <48B7090C.3030506@zytor.com> (raw)
In-Reply-To: <48B70660.5020003@goop.org>
Jeremy Fitzhardinge wrote:
> H. Peter Anvin wrote:
>> +#define X86_FEATURE_VMX (4*32+ 5) /* Hardware virtualization */
>> +#define X86_FEATURE_SMX (4*32+ 6) /* "Safer" mode */
>>
> Is this supposed to appear as "Safer" in /proc/cpuinfo? Or should this
> be ``Safer''?
It was a dumb-ass thinko on my part (already fixed in tip:x86/cpu).
-hpa
prev parent reply other threads:[~2008-08-28 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 4:30 Cleanup and updates of x86 CPU definitions H. Peter Anvin
2008-08-28 20:11 ` Jeremy Fitzhardinge
2008-08-28 20:22 ` H. Peter Anvin [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=48B7090C.3030506@zytor.com \
--to=hpa@zytor.com \
--cc=austin_zhang@linux.intel.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=x86@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