[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <871pzxzuny.ffs@tglx>
Date: Wed, 30 Oct 2024 12:39:45 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Thomas Weißschuh <thomas.weissschuh@...utronix.de>, Guo
Ren
<guoren@...nel.org>, Heiko Carstens <hca@...ux.ibm.com>, Vasily Gorbik
<gor@...ux.ibm.com>, Alexander Gordeev <agordeev@...ux.ibm.com>, Christian
Borntraeger <borntraeger@...ux.ibm.com>, Sven Schnelle
<svens@...ux.ibm.com>, Catalin Marinas <catalin.marinas@....com>, Will
Deacon <will@...nel.org>, Paul Walmsley <paul.walmsley@...ive.com>, Palmer
Dabbelt <palmer@...belt.com>, Albert Ou <aou@...s.berkeley.edu>, Russell
King <linux@...linux.org.uk>, Huacai Chen <chenhuacai@...nel.org>, WANG
Xuerui <kernel@...0n.name>, Theodore Ts'o <tytso@....edu>, "Jason A.
Donenfeld" <Jason@...c4.com>, Thomas Bogendoerfer
<tsbogend@...ha.franken.de>, Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>, Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>, Michael Ellerman
<mpe@...erman.id.au>, Nicholas Piggin <npiggin@...il.com>, Christophe
Leroy <christophe.leroy@...roup.eu>, Naveen N Rao <naveen@...nel.org>,
Madhavan Srinivasan <maddy@...ux.ibm.com>, Vincenzo Frascino
<vincenzo.frascino@....com>
Cc: Christophe Leroy <christophe.leroy@...roup.eu>,
linux-csky@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-s390@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-riscv@...ts.infradead.org, loongarch@...ts.linux.dev,
linux-mips@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org, Thomas
Weißschuh <thomas.weissschuh@...utronix.de>, Nam Cao
<namcao@...utronix.de>
Subject: Re: [PATCH 00/28] vdso: Preparations for generic data storage
Folks!
On Thu, Oct 10 2024 at 09:01, Thomas Weißschuh wrote:
> Historically each architecture defined their own datapage to store the
> VDSO data. This stands in contrast to the generic nature of the VDSO
> code itself.
> We plan to introduce a generic framework for the management of the VDSO
> data storage that can be used by all architectures and which works
> together with the existing generic VDSO code.
>
> Before that is possible align the different architectures by
> standardizing on the existing generic infrastructure and moving things
> out of the VDSO data page which does not belong there.
>
> Patches 1- 2: csky
> Patch 3: s390
> Patches 4- 5: arm64
> Patch 6: riscv
> Patch 7: arm
> Patch 8: LoongArch
> Patch 9: MIPS
> Patches 10-20: x86
> Patches 21-27: powerpc
> Patch 28: Renamings to avoid a name clash with the new code.
As this has been sitting for two weeks now without major comments, I'm
planning to merge that through the tip tree tomorrow.
Thanks,
tglx
Powered by blists - more mailing lists