[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b706e37d-66c1-4666-89a2-03c6bb58bb2a@intel.com>
Date: Fri, 21 Feb 2025 09:37:51 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Dmitry Vyukov <dvyukov@...gle.com>, mathieu.desnoyers@...icios.com,
peterz@...radead.org, boqun.feng@...il.com, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com, hpa@...or.com,
aruna.ramakrishna@...cle.com, elver@...gle.com
Cc: "Paul E. McKenney" <paulmck@...nel.org>, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] pkeys: add API to switch to permissive pkey register
On 2/17/25 03:07, Dmitry Vyukov wrote:
> arch/x86/Kconfig | 1 +
> arch/x86/include/asm/pkeys.h | 14 ++++++++++++++
> arch/x86/include/asm/pkru.h | 10 +++++++---
> include/linux/pkeys.h | 22 ++++++++++++++++++++++
> mm/Kconfig | 2 ++
One last thought...
This is touching x86, mm and rseq code. So, who's going to send it to Linus?
I'm happy to send this in one of the tip branches and send it upstream.
But I'd also be happy to provide acks and have it go up with other rseq
bits.
Does anyone have a preference?
Powered by blists - more mailing lists