From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: mingo@elte.hu, jeremy@goop.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] x86: enlightenment for ticket spinlocks
Date: Mon, 01 Feb 2010 08:40:15 -0800 [thread overview]
Message-ID: <4B6703EF.9050306@zytor.com> (raw)
In-Reply-To: <4B669742020000780002CEEB@vpn.id2.novell.com>
On 01/31/2010 11:56 PM, Jan Beulich wrote:
>>
>> It's probably a bug that's now cast in stone. That happends. I just
>> had to be picky. (And yes, it's ebx-edx-ecx; see my second email.)
>
> The "good" thing is that this is not on leaf 0, but on leaf 0x4000??00,
> i.e. "normal" code would never display this garbled string.
>
Well, yes, but the format of ID leaves is the same between groups.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2010-02-01 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 18:02 [PATCH 0/3] x86: enlightenment for ticket spinlocks Jan Beulich
2010-01-31 18:43 ` H. Peter Anvin
2010-02-01 7:56 ` Jan Beulich
2010-02-01 16:40 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-29 8:00 Jan Beulich
2010-01-31 1:42 ` H. Peter Anvin
2010-01-31 1:45 ` H. Peter Anvin
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=4B6703EF.9050306@zytor.com \
--to=hpa@zytor.com \
--cc=JBeulich@novell.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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.