From: josh@joshtriplett.org
To: Andy Lutomirski <luto@amacapital.net>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org, mingo@kernel.org
Subject: Re: [PATCH 0/3] x86_64: Tidy up vsyscall emulation and make it optional
Date: Tue, 28 Oct 2014 10:46:33 -0700 [thread overview]
Message-ID: <20141028174633.GB12195@cloud> (raw)
In-Reply-To: <cover.1414516558.git.luto@amacapital.net>
On Tue, Oct 28, 2014 at 10:22:25AM -0700, Andy Lutomirski wrote:
> 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
Nice!
For patches 1 and 2:
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
For patch 3, I responded with a possible minor improvement, but with or
without that:
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
I assume these should go through tip/x86/vdso as well?
Also, any plans to do something similar for vsyscall_gtod.c?
- Josh Triplett
next prev parent reply other threads:[~2014-10-28 17:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 17:22 [PATCH 0/3] x86_64: Tidy up vsyscall emulation and make it optional Andy Lutomirski
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 ` [PATCH 3/3] x86_64, vsyscall: " Andy Lutomirski
2014-10-29 21:30 ` [PATCH 3/3] x86_64,vsyscall: " Andy Lutomirski
2014-12-01 15:33 ` Konrad Rzeszutek Wilk
2014-12-01 23:18 ` Andy Lutomirski
2014-12-01 23:18 ` [PATCH 3/3] x86_64, vsyscall: " Andy Lutomirski
2014-12-01 15:33 ` Konrad Rzeszutek Wilk
2014-10-29 20:00 ` Konrad Rzeszutek Wilk
2014-10-28 18:09 ` Andy Lutomirski
2014-10-28 17:46 ` josh [this message]
2014-10-28 18:04 ` [PATCH 0/3] x86_64: Tidy up vsyscall emulation and make it optional 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=20141028174633.GB12195@cloud \
--to=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.