[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrUGc5+CS8=sYvtkK967ZR833zu98rzRkEw_DX++1hL-BA@mail.gmail.com>
Date: Wed, 12 Mar 2014 14:49:06 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: "H. Peter Anvin" <hpa@...ux.intel.com>,
Stefani Seibold <stefani@...bold.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"the arch/x86 maintainers" <x86@...nel.org>,
Dave Jones <davej@...hat.com>,
Martin Runge <Martin.Runge@...de-schwarz.com>,
Andreas Brief <Andreas.Brief@...de-schwarz.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v2] x86: Remove compat vdso support
On Wed, Mar 12, 2014 at 2:46 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> On Wed, Mar 12, 2014 at 2:37 PM, H. Peter Anvin <hpa@...ux.intel.com> wrote:
>>
>> How would that deal with the legacy vsyscall case for x86-64? Just rely
>> on the "legacy vsyscall emulation" (which seems to have its own class of
>> problems...)?
>
> It does?
>
> We *default* to emulation, and have for over two years now (since
> v3.4). If there are problems with it, we need to fix those.
Even in the non-default "vsyscall=native" case, the vsyscall pages
just contains syscalls. It does not need to access the vvar page, the
hpet, or anything else that the vdso uses.
>
> Linus
--
Andy Lutomirski
AMA Capital Management, LLC
--
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