[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAObL_7Ge7PDSqt8sfBAODDnuA34oCsA4Lat24RXGe1DPAKdXqA@mail.gmail.com>
Date: Wed, 10 Aug 2011 13:47:13 -0400
From: Andrew Lutomirski <luto@....edu>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: x86@...nel.org, Andi Kleen <andi@...stfloor.org>,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
lueckintel@...oo.com, kimwooyoung@...il.com,
Ingo Molnar <mingo@...e.hu>, Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH 3/3] x86-64: Rework vsyscall emulation and add vsyscall= parameter
On Wed, Aug 10, 2011 at 1:21 PM, H. Peter Anvin <hpa@...or.com> wrote:
> On 08/10/2011 10:15 AM, Andy Lutomirski wrote:
>> There are three choices:
>>
>> vsyscall=native: Vsyscalls are native code that issues the
>> corresponding syscalls.
>>
>> vsyscall=emulate (default): Vsyscalls are emulated by instruction
>> fault traps, tested in the bad_area path. The actual contents of
>> the vsyscall page is the same as the vsyscall=native case except
>> that it's marked NX. This way programs that make assumptions about
>> what the code in the page does will not be confused when they read
>> that code.
>>
>> vsyscall=none: Trying to execute a vsyscall will segfault.
>>
>> Signed-off-by: Andy Lutomirski <luto@....edu>
>
> Hi Andy,
>
> This patch doesn't apply. What is your baseline for this patch?
My baseline was a commit that probably only lives in my tree, but the
patches should apply cleanly on top of
c149a665ac488e0dac22a42287f45ad1bda06ff1, which is the current
tip/x86/vdso.
--Andy
--
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/
Powered by blists - more mailing lists