[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMzpN2j1-Pa0JrVBnpFJHV++-Kw7FjSvf1gEYy1+HZNJHt-CUQ@mail.gmail.com>
Date: Wed, 12 Mar 2014 12:18:10 -0400
From: Brian Gerst <brgerst@...il.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Stefani Seibold <stefani@...bold.net>,
Andy Lutomirski <luto@...capital.net>,
"H. Peter Anvin" <hpa@...ux.intel.com>,
"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 12:04 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> On Wed, Mar 12, 2014 at 8:46 AM, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
>>
>> But I think that "x86, vdso: Add 32 bit VDSO time support for 32 bit
>> kernel" patch needs to die. And the helper patches building up to it
>> (just because that patch used [io_]remap_pfn_range()) should die too.
>> Why weren't those pages in the vdso*_pages[] array anyway?
>
> Sorry, confused. FIXMAP, not vdso_pages.
>
> Anyway, that's what x86-64 does. Why not 32?
A 32-bit process running on a 64-bit kernel cannot access the high
fixmap mappings. The VVAR/HPET pages have to be mapped below 4GB.
--
Brian Gerst
--
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