From: Ingo Molnar <mingo@kernel.org>
To: Andrew Lutomirski <luto@mit.edu>
Cc: Andi Kleen <andi@firstfloor.org>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
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>,
Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: NACK! Re: [PATCH 4/4] Add vsyscalls to feature-removal-schedule.txt
Date: Wed, 17 Aug 2011 22:35:17 +0200 [thread overview]
Message-ID: <20110817203517.GF16512@kernel.org> (raw)
In-Reply-To: <CAObL_7HCqoBT_YY+mtb7wcAAHd1pxuACp8kZ62M47KAqjzLHNQ@mail.gmail.com>
* Andrew Lutomirski <luto@mit.edu> wrote:
> Somewhat to my surprise, fully up-to-date Fedora 15 seems to work
> fine with vsyscall=none, and I wouldn't be terribly surprised if a
> few of the distributions starting making it the default sooner or
> later. I might do a followup patch to make the switch betweeen
> vsyscall=emulate and vsyscall=none work as a sysctl. (Switching
> from native to emulate at runtime could be problematic.)
As long as no binaries break (emulation is fine) it's perfectly fine
to phase out the executable vsyscall page and keep it as a data page
only - and we can put that into feature-removal-schedule.txt just
fine.
Thanks,
Ingo
prev parent reply other threads:[~2011-08-17 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 14:27 [PATCH 0/4] vsyscall tweaks Andy Lutomirski
2011-08-09 14:27 ` [PATCH 1/4] x86-64: Allow emulated vsyscalls from user addresses Andy Lutomirski
2011-08-09 18:59 ` H. Peter Anvin
2011-08-09 19:16 ` Andrew Lutomirski
2011-08-09 14:27 ` [PATCH 2/4] x86: Remove unnecessary compile flag tweaks for vsyscall code Andy Lutomirski
2011-08-09 14:27 ` [PATCH 3/4] x86-64: Wire up getcpu syscall Andy Lutomirski
2011-08-09 14:27 ` [PATCH 4/4] Add vsyscalls to feature-removal-schedule.txt Andy Lutomirski
2011-08-12 18:25 ` NACK! " Andi Kleen
2011-08-12 19:13 ` Andrew Lutomirski
2011-08-17 20:35 ` Ingo Molnar [this message]
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=20110817203517.GF16512@kernel.org \
--to=mingo@kernel.org \
--cc=andi@firstfloor.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=kimwooyoung@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lueckintel@yahoo.com \
--cc=luto@mit.edu \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--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