From: Peter Zijlstra <peterz@infradead.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
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>,
"open list:MIPS" <linux-mips@vger.kernel.org>,
"open list:S390" <linux-s390@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] jump_label: make initial NOP patching the special case
Date: Fri, 17 Jun 2022 15:40:20 +0200 [thread overview]
Message-ID: <YqyERLVg45bi0pCJ@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <CAMj1kXFfVi8sYXR0z42v72XfTBaQ9jaDAzuLuK=TBKHUqKkEPA@mail.gmail.com>
On Thu, Jun 16, 2022 at 01:25:02PM +0200, Ard Biesheuvel wrote:
> On Wed, 15 Jun 2022 at 17:41, Ard Biesheuvel <ardb@kernel.org> 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>
> > Acked-by: Mark Rutland <mark.rutland@arm.com>
> > Acked-by: Peter Zijlstra (Intel) <peterz@infradead.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, 7 insertions(+), 83 deletions(-)
> >
>
> This needs the following hunk as well, as spotted by the bot:
>
> --- a/include/linux/jump_label.h
> +++ b/include/linux/jump_label.h
> @@ -220,8 +220,6 @@ extern void jump_label_lock(void);
> extern void jump_label_unlock(void);
> extern void arch_jump_label_transform(struct jump_entry *entry,
> enum jump_label_type type);
> -extern void arch_jump_label_transform_static(struct jump_entry *entry,
> - enum jump_label_type type);
> extern bool arch_jump_label_transform_queue(struct jump_entry *entry,
> enum jump_label_type type);
> extern void arch_jump_label_transform_apply(void);
>
Done, Thanks!
next prev parent reply other threads:[~2022-06-17 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 15:41 [PATCH v2 0/3] jump_label: get rid of NOP patching where possible Ard Biesheuvel
2022-06-15 15:41 ` [PATCH v2 1/3] jump_label: s390: avoid pointless initial NOP patching Ard Biesheuvel
2022-06-26 7:57 ` Alexander Gordeev
2022-06-28 7:09 ` [tip: locking/core] " tip-bot2 for Ard Biesheuvel
2022-06-15 15:41 ` [PATCH v2 2/3] jump_label: mips: move module NOP patching into arch code Ard Biesheuvel
2022-06-26 8:03 ` Alexander Gordeev
2022-06-28 7:09 ` [tip: locking/core] " tip-bot2 for Ard Biesheuvel
2022-06-15 15:41 ` [PATCH v2 3/3] jump_label: make initial NOP patching the special case Ard Biesheuvel
2022-06-16 11:25 ` Ard Biesheuvel
2022-06-17 13:40 ` Peter Zijlstra [this message]
2022-06-26 8:04 ` Alexander Gordeev
2022-06-28 7:09 ` [tip: locking/core] " tip-bot2 for 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=YqyERLVg45bi0pCJ@worktop.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
Powered by JetHome