From: Juergen Gross <jgross@suse.com>
To: linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v4 0/3] x86/alternative: Patch a single alternative location only once
Date: Mon, 15 Dec 2025 09:25:13 +0100 [thread overview]
Message-ID: <bd461faf-65c8-4c13-837d-fedefef588f5@suse.com> (raw)
In-Reply-To: <20251119160420.22160-1-jgross@suse.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1082 bytes --]
Ping?
On 19.11.25 17:04, Juergen Gross wrote:
> Instead of patching a single location potentially multiple times in
> case of nested ALTERNATIVE()s, do the patching only after having
> evaluated all alt_instr instances for that location.
>
> Changes in V2:
> - complete rework (Boris Petkov)
>
> Changes in V3:
> - split former V2 patch into 2 by introducing a helper function (Boris Petkov)
> - repost the small cleanup patch 1 which was taken before, but has somehow
> vanished from the tip x86/alternative branch (it is still in the tip
> master branch, but I couldn't find it in any other tip branch).
>
> Changes in V4:
> - use 3 helpers instead of 1 (Boris Petkov)
>
> Juergen Gross (3):
> x86/alternative: Drop not needed test after call of alt_replace_call()
> x86/alternative: Use helper functions for patching alternatives
> x86/alternative: Patch a single alternative location only once
>
> arch/x86/kernel/alternative.c | 147 ++++++++++++++++++++--------------
> 1 file changed, 87 insertions(+), 60 deletions(-)
>
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2025-12-15 8:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 16:04 [PATCH v4 0/3] x86/alternative: Patch a single alternative location only once Juergen Gross
2025-11-19 16:04 ` [PATCH v4 1/3] x86/alternative: Drop not needed test after call of alt_replace_call() Juergen Gross
2025-11-19 16:04 ` [PATCH v4 2/3] x86/alternative: Use helper functions for patching alternatives Juergen Gross
2026-01-02 13:00 ` Borislav Petkov
2025-11-19 16:04 ` [PATCH v4 3/3] x86/alternative: Patch a single alternative location only once Juergen Gross
2026-01-02 16:05 ` Borislav Petkov
2025-12-15 8:25 ` Juergen Gross [this message]
2025-12-15 10:25 ` [PATCH v4 0/3] " 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=bd461faf-65c8-4c13-837d-fedefef588f5@suse.com \
--to=jgross@suse.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox