[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CALCETrX=OCu14inB_v1zTtjVJx3EK5Ar6+QzBVc1seUnTmnz3g@mail.gmail.com>
Date:	Tue, 1 Apr 2014 14:57:43 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	"H. Peter Anvin" <hpa@...or.com>, X86 ML <x86@...nel.org>
Cc:	Stefani Seibold <stefani@...bold.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andy Lutomirski <luto@...capital.net>
Subject: Re: [PATCH 0/6] x86: Clean up and unify the vdso
On Sun, Mar 30, 2014 at 9:53 AM, Andy Lutomirski <luto@...capital.net> wrote:
> This rewrites a bunch of the vdso code.  After these patches, the vvar
> and hpet pages are mapped directly after the vdso text on all five vdso
> variants.  The fixmaps are gone on 64-bit systems.
>
> It would be possible to build the x32 vdso the normal way on top of
> these patches.
>
> I haven't touched the pvclock code.  I'd want to understand why it
> exists, why it isn't using rdtsc, and why it has two rdtsc_barrier calls
> before rearranging it.
>
> This is most likely 3.16 material.
>
> Andy Lutomirski (6):
>   x86: Clean up 32-bit vs 64-bit vdso params
>   x86: Move syscall and sysenter setup into kernel/cpu/common.c
>   x86: Reimplement vdso.so preparation in build-time C
This breaks gold.  I'll submit a v2 after the merge window with a fix.
 (It's a trivial change to the linker script and shouldn't
meaningfully affect any effort to review this series.)
>   x86: Move the 32-bit vdso special pages after the text
>   x86: Move the vvar and hpet mappings next to the 64-bit vDSO
>   x86: Remove vestiges of VDSO_PRELINK and some outdated comments
--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