linux-kernel - Re: [PATCH 0/3] x86: enlightenment for ticket spinlocks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4B65CF5B.3000804@zytor.com>
Date:	Sun, 31 Jan 2010 10:43:39 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jan Beulich <jbeulich@...ell.com>
CC:	mingo@...e.hu, jeremy@...p.org, tglx@...utronix.de,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] x86: enlightenment for ticket spinlocks

On 01/31/2010 10:02 AM, Jan Beulich wrote:
>>>> "H. Peter Anvin"  01/31/10 2:42 AM >>>
>> + * EBX-EDX: "XenVMMXenVMM" signature, allowing positive identification
>> + *      of a Xen host.
>> + */
>> +#define XEN_CPUID_SIGNATURE_EBX 0x566e6558 /* "XenV" */
>> +#define XEN_CPUID_SIGNATURE_ECX 0x65584d4d /* "MMXe" */
>> +#define XEN_CPUID_SIGNATURE_EDX 0x4d4d566e /* "nVMM" */
>>
>> I hope you know this spells "MMXenVMMXenV".  The ordering is ecx-edx-ebx
>> (register numbers 1, 2, 3).
> 
> According to the documentation I have, the ordering is EBX-EDX-ECX,
> so indeed the spelling would seem broken, but since this is an interface
> header taken directly from Xen, it's got to be (and it works) that way.
> Odd.
> 

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

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/