From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@mit.edu>
Cc: x86@kernel.org, Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
lueckintel@yahoo.com, kimwooyoung@gmail.com,
Ingo Molnar <mingo@elte.hu>, Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH 3/3] x86-64: Rework vsyscall emulation and add vsyscall= parameter
Date: Wed, 10 Aug 2011 12:21:03 -0500 [thread overview]
Message-ID: <4E42BDFF.5060507@zytor.com> (raw)
In-Reply-To: <8449fb3abf89851fd6b2260972666a6f82542284.1312988155.git.luto@mit.edu>
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@mit.edu>
Hi Andy,
This patch doesn't apply. What is your baseline for this patch?
-hpa
next prev parent reply other threads:[~2011-08-10 17:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 15:15 [PATCH 0/3] vsyscall emulation compatibility fixes Andy Lutomirski
2011-08-10 15:15 ` [PATCH 1/3] x86: Remove unnecessary compile flag tweaks for vsyscall code Andy Lutomirski
2011-08-11 0:01 ` [tip:x86/vdso] " tip-bot for Andy Lutomirski
2011-08-10 15:15 ` [PATCH 2/3] x86-64: Wire up getcpu syscall Andy Lutomirski
2011-08-11 0:01 ` [tip:x86/vdso] " tip-bot for Andy Lutomirski
2011-08-11 0:31 ` tip-bot for Andy Lutomirski
2011-08-10 15:15 ` [PATCH 3/3] x86-64: Rework vsyscall emulation and add vsyscall= parameter Andy Lutomirski
2011-08-10 17:21 ` H. Peter Anvin [this message]
2011-08-10 17:47 ` Andrew Lutomirski
2011-08-10 21:14 ` H. Peter Anvin
2011-08-10 21:18 ` Andrew Lutomirski
2011-08-10 22:20 ` H. Peter Anvin
2011-08-10 22:56 ` Andrew Lutomirski
2011-08-11 0:02 ` [tip:x86/vdso] " tip-bot for Andy Lutomirski
2011-08-11 0:31 ` tip-bot for Andy Lutomirski
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=4E42BDFF.5060507@zytor.com \
--to=hpa@zytor.com \
--cc=andi@firstfloor.org \
--cc=bp@alien8.de \
--cc=kimwooyoung@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lueckintel@yahoo.com \
--cc=luto@mit.edu \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).