[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAObL_7HCqoBT_YY+mtb7wcAAHd1pxuACp8kZ62M47KAqjzLHNQ@mail.gmail.com>
Date: Fri, 12 Aug 2011 15:13:42 -0400
From: Andrew Lutomirski <luto@....edu>
To: Andi Kleen <andi@...stfloor.org>
Cc: x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
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>,
Suresh Siddha <suresh.b.siddha@...el.com>
Subject: Re: NACK! Re: [PATCH 4/4] Add vsyscalls to feature-removal-schedule.txt
On Fri, Aug 12, 2011 at 2:25 PM, Andi Kleen <andi@...stfloor.org> wrote:
> Andy Lutomirski <luto@....EDU> writes:
>
>> In a couple years, we'll see how well we've done at eradicating vsyscall-using
>> binaries. Hopefully we can then disable them by default. We will probably
>> have to leave the option to enable them around forever.
>
> NACK NACK NACK!
>
It's already dropped from the version in tip/x86/vdso.
> this would break all old (old = meaning all today's) x86-64 installations.
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.)
--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