From: Peter Zijlstra <peterz@infradead.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
linux-kernel@vger.kernel.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
linux-mips@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH 3/3] jump_label: make initial NOP patching the special case
Date: Wed, 15 Jun 2022 12:06:39 +0200 [thread overview]
Message-ID: <YqmvL2Biw3TnIl7a@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <Yqmr6fvu4OYkarCm@FVFF77S0Q05N>
On Wed, Jun 15, 2022 at 10:52:41AM +0100, Mark Rutland wrote:
> On Wed, Jun 08, 2022 at 12:45:12PM +0200, Ard Biesheuvel wrote:
> > Instead of defaulting to patching NOP opcodes at init time, and leaving
> > it to the architectures to override this if this is not needed, switch
> > to a model where doing nothing is the default. This is the common case
> > by far, as only MIPS requires NOP patching at init time. On all other
> > architectures, the correct encodings are emitted by the compiler and so
> > no initial patching is needed.
> >
> > Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> > ---
> > Documentation/staging/static-keys.rst | 3 ---
> > arch/arc/kernel/jump_label.c | 13 -------------
> > arch/arm/kernel/jump_label.c | 6 ------
> > arch/arm64/kernel/jump_label.c | 11 -----------
> > arch/mips/include/asm/jump_label.h | 2 ++
> > arch/parisc/kernel/jump_label.c | 11 -----------
> > arch/riscv/kernel/jump_label.c | 12 ------------
> > arch/s390/kernel/jump_label.c | 5 -----
> > arch/x86/kernel/jump_label.c | 13 -------------
> > kernel/jump_label.c | 14 +++-----------
> > 10 files changed, 5 insertions(+), 85 deletions(-)
>
> I have one minor comment below, but either way this is a nice cleanup (and I'm
> always happy to see __weak functions disappear), so FWIW:
(I've got a new found hatred for __weak after having had to fix so many
objtool issues with it, so yeah, that).
>
> Acked-by: Mark Rutland <mark.rutland@arm.com>
With the thing Mark pointed out fixed:
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
(although, I'll probably be the one to eventually apply these I suppose,
unless they're needed in a different tree?)
next prev parent reply other threads:[~2022-06-15 10:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 10:45 [PATCH 0/3] jump_label: get rid of NOP patching where possible Ard Biesheuvel
2022-06-08 10:45 ` [PATCH 1/3] jump_label: s390: avoid pointless initial NOP patching Ard Biesheuvel
2022-06-08 10:45 ` [PATCH 2/3] jump_label: mips: move module NOP patching into arch code Ard Biesheuvel
2022-06-08 10:45 ` [PATCH 3/3] jump_label: make initial NOP patching the special case Ard Biesheuvel
2022-06-15 9:52 ` Mark Rutland
2022-06-15 9:58 ` Ard Biesheuvel
2022-06-15 10:06 ` Peter Zijlstra [this message]
2022-06-15 10:20 ` Ard Biesheuvel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YqmvL2Biw3TnIl7a@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=agordeev@linux.ibm.com \
--cc=ardb@kernel.org \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=svens@linux.ibm.com \
--cc=tsbogend@alpha.franken.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox