From: Borislav Petkov <bp@alien8.de>
To: X86 ML <x86@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/4] x86/alternatives: Do NOPs optimization on a temporary buffer
Date: Sun, 31 Mar 2024 20:00:38 +0200 [thread overview]
Message-ID: <20240331180042.13933-1-bp@alien8.de> (raw)
From: "Borislav Petkov (AMD)" <bp@alien8.de>
Hi,
here's v2 of the set to do NOPs optimizations on a temporary buffer
after the last-minute conflict and resulting breakage before the last
merge window which made me retract those.
This v2 has been extensively tested on 6.9-rc1.
Thx.
Changelog:
=========
v0:
here's a small set which sprang out from my reacting to the fact that
NOPs optimization in the alternatives code needs to happen on
a temporary buffer like the other alternative operations - not in-place
and cause all kinds of fun.
The result is this, which makes the alternatives code simpler and it is
a net win, size-wise:
1 file changed, 50 insertions(+), 72 deletions(-)
Constructive feedback is always welcome!
Borislav Petkov (AMD) (4):
x86/alternatives: Use a temporary buffer when optimizing NOPs
x86/alternatives: Get rid of __optimize_nops()
x86/alternatives: Optimize optimize_nops()
x86/alternatives: Sort local vars in apply_alternatives()
arch/x86/include/asm/text-patching.h | 2 +-
arch/x86/kernel/alternative.c | 133 ++++++++++++---------------
arch/x86/kernel/callthunks.c | 9 +-
3 files changed, 62 insertions(+), 82 deletions(-)
--
2.43.0
next reply other threads:[~2024-03-31 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 18:00 Borislav Petkov [this message]
2024-03-31 18:00 ` [PATCH v2 1/4] x86/alternatives: Use a temporary buffer when optimizing NOPs Borislav Petkov
2024-03-31 18:00 ` [PATCH v2 2/4] x86/alternatives: Get rid of __optimize_nops() Borislav Petkov
2024-03-31 18:00 ` [PATCH v2 3/4] x86/alternatives: Optimize optimize_nops() Borislav Petkov
2024-03-31 18:00 ` [PATCH v2 4/4] x86/alternatives: Sort local vars in apply_alternatives() Borislav Petkov
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=20240331180042.13933-1-bp@alien8.de \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.