From: Andy Lutomirski <luto@amacapital.net>
To: x86@kernel.org, linux-kernel@vger.kernel.org,
Josh Triplett <josh@joshtriplett.org>
Cc: mingo@kernel.org, Andy Lutomirski <luto@amacapital.net>
Subject: [PATCH 0/3] x86_64: Tidy up vsyscall emulation and make it optional
Date: Tue, 28 Oct 2014 10:22:25 -0700 [thread overview]
Message-ID: <cover.1414516558.git.luto@amacapital.net> (raw)
Now that arch/x86/kernel/vsyscall_64.c contains only vsyscall
emulation code, clean it up and make it optional.
Patch 1 makes vsyscall=none work be a bit more self-consistent: it
actually removes the fake vsyscall page instead of just segfaulting
anyone who tries to use it.
Patch 2 is pure cosmetic cleanup.
Patch 3 is the meat: it lets vsyscall emulation be configured out.
The config option to disable it is hidden under CONFIG_EXPERT, since
it will break legacy code.
Note that, last I checked, current userspace is unlikely to work if
the vDSO *and* vsyscalls are off. Take it up with the glibc
maintainers.
This applies on top of tip/x86/vdso.
Andy Lutomirski (3):
x86_64,vsyscall: Turn vsyscalls all the way off when vsyscall=none
x86_64,vsyscall: Rewrite comment and clean up headers in vsyscall code
x86_64,vsyscall: Make vsyscall emulation configurable
arch/x86/Kconfig | 18 ++++++++++++
arch/x86/include/asm/fixmap.h | 2 ++
arch/x86/include/asm/page_64.h | 4 ++-
arch/x86/include/asm/vsyscall.h | 8 +++++
arch/x86/kernel/Makefile | 3 +-
arch/x86/kernel/setup.c | 2 --
arch/x86/kernel/vsyscall_64.c | 65 +++++++++++++++++------------------------
arch/x86/xen/mmu.c | 6 ++--
8 files changed, 63 insertions(+), 45 deletions(-)
--
1.9.3
next reply other threads:[~2014-10-28 17:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 17:22 Andy Lutomirski [this message]
2014-10-28 17:22 ` [PATCH 1/3] x86_64,vsyscall: Turn vsyscalls all the way off when vsyscall=none Andy Lutomirski
2014-10-28 17:22 ` [PATCH 2/3] x86_64,vsyscall: Rewrite comment and clean up headers in vsyscall code Andy Lutomirski
2014-10-28 17:22 ` [PATCH 3/3] x86_64,vsyscall: Make vsyscall emulation configurable Andy Lutomirski
2014-10-28 17:57 ` Josh Triplett
2014-10-28 18:09 ` Andy Lutomirski
2014-10-29 20:00 ` Konrad Rzeszutek Wilk
2014-10-29 21:30 ` Andy Lutomirski
2014-12-01 15:33 ` Konrad Rzeszutek Wilk
2014-12-01 23:18 ` Andy Lutomirski
2014-10-28 17:46 ` [PATCH 0/3] x86_64: Tidy up vsyscall emulation and make it optional josh
2014-10-28 18:04 ` 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=cover.1414516558.git.luto@amacapital.net \
--to=luto@amacapital.net \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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