[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jLSiYhUtq6tEXqzV6KT5tY-T1ds_bCE1=pb-GKddneEAg@mail.gmail.com>
Date: Mon, 29 Apr 2013 10:52:58 -0700
From: Kees Cook <keescook@...omium.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, "x86@...nel.org" <x86@...nel.org>,
Jarkko Sakkinen <jarkko.sakkinen@...el.com>, Matthew Garrett <mjg@...hat.com>,
Matt Fleming <matt.fleming@...el.com>, Eric Northup <digitaleric@...gle.com>,
Dan Rosenberg <drosenberg@...curity.com>, Julien Tinnes <jln@...gle.com>,
Will Drewry <wad@...omium.org>
Subject: Re: [PATCH 2/6] x86: kaslr: move CPU flags out of cpucheck
On Mon, Apr 29, 2013 at 10:49 AM, Kees Cook <keescook@...omium.org> wrote:
> On Fri, Apr 26, 2013 at 3:14 PM, H. Peter Anvin <hpa@...or.com> wrote:
>> On 04/26/2013 02:47 PM, H. Peter Anvin wrote:
>>> On 04/26/2013 12:03 PM, Kees Cook wrote:
>>>> +
>>>> +static inline void cpuid(u32 id, u32 *a, u32 *b, u32 *c, u32 *d)
>>>> +{
>>>> + /* Handle x86_32 PIC using ebx. */
>>>> + asm volatile("movl %%ebx, %%edi \n\t"
>>>> + "cpuid \n\t"
>>>> + "xchgl %%edi, %%ebx\n\t"
>>>> + : "=a" (*a),
>>>> + "=D" (*b),
>>>> + "=c" (*c),
>>>> + "=d" (*d)
>>>> + : "a" (id)
>>>> + );
>>>> +}
>>>
>>> Please don't constrain registers unnecessarily.
>>>
>>> You can use "=r" there and let gcc assign whatever free register it pleases.
>>>
>>> You can also limit that to only:
>>>
>>> #if defined(__i386__) && defined(__PIC__)
>>>
>>
>> How is this for a "beauty":
>>
>>
>> #if defined(__i386__) && defined (__PIC__)
>> # define EBX_REG "=r"
>> #else
>> # define EBX_REG "=b"
>> #endif
>>
>> asm volatile(".ifnc %%ebx,%3 ; movl %%ebx,%3 ; .endif ; "
>> "cpuid ; "
>> ".ifnc %%ebx,%3 ; xchgl %%ebx,%3 ; .endif"
>> : "=a" (*a), "=c" (*c), "=d" (*d),
>> EBX_REG (*b)
>> : "a" (leaf), "c" (subleaf));
>>
>
> Oh, very nice on the ifnc and register define! Is the leaf/subleaf
> stuff needed there? That piece doesn't make sense to me.
Ah, nevermind, I just need the "leaf" bit for the cpuid input. Thanks!
-Kees
--
Kees Cook
Chrome OS Security
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
