From: Mike Rapoport <rppt@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
x86@kernel.org, Bert Karwatzki <spasswolf@web.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>, Thomas Gleixner <tglx@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/alternative: Drop smp_locks glue
Date: Sun, 14 Jun 2026 12:39:30 +0300 [thread overview]
Message-ID: <ai520hrj16qUiBVp@kernel.org> (raw)
In-Reply-To: <20260613185632.GAai2n4GkGXFsBm6gT@fat_crate.local>
On Sat, Jun 13, 2026 at 11:56:32AM -0700, Borislav Petkov wrote:
> From: "Borislav Petkov (AMD)" <bp@alien8.de>
> Date: Sat, 13 Jun 2026 10:15:27 -0700
>
> This was there to be able to patch out locking instructions when running
> a SMP kernel build on a UP CPU. The times are long gone when single-CPU
> x86 machines were relevant so drop that machinery and simplify the code
> considerably.
>
> LOCK_PREFIX needs to stay for when one wants to do a UP build for
> whatever reason. That'll go away when CONFIG_SMP becomes unconditional.
>
> Kill a bunch of leftover, unused prototypes while at it.
>
> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
FWIW:
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> arch/um/kernel/um_arch.c | 12 --
> arch/x86/include/asm/alternative.h | 47 +------
> arch/x86/include/asm/cmpxchg_32.h | 4 +-
> arch/x86/kernel/alternative.c | 190 -----------------------------
> arch/x86/kernel/kprobes/core.c | 3 -
> arch/x86/kernel/kprobes/opt.c | 1 -
> arch/x86/kernel/module.c | 13 +-
> arch/x86/kernel/smpboot.c | 3 -
> arch/x86/kernel/vmlinux.lds.S | 12 --
> arch/x86/tools/relocs.c | 2 +-
> tools/objtool/check.c | 1 -
> tools/objtool/klp-diff.c | 1 -
> 12 files changed, 9 insertions(+), 280 deletions(-)
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2026-06-14 9:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 8:16 [PATCH] x86/alternative: delay freeing of smp_locks section Mike Rapoport
2026-03-28 11:41 ` Borislav Petkov
2026-03-28 12:39 ` Mike Rapoport
2026-03-28 19:58 ` Borislav Petkov
2026-03-30 17:16 ` Mike Rapoport
2026-03-30 17:44 ` Borislav Petkov
2026-03-30 19:36 ` Peter Zijlstra
2026-03-30 19:43 ` H. Peter Anvin
2026-03-30 20:20 ` Borislav Petkov
2026-06-13 18:56 ` [PATCH] x86/alternative: Drop smp_locks glue Borislav Petkov
2026-06-13 20:17 ` Peter Zijlstra
2026-06-14 9:39 ` Mike Rapoport [this message]
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=ai520hrj16qUiBVp@kernel.org \
--to=rppt@kernel.org \
--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=peterz@infradead.org \
--cc=spasswolf@web.de \
--cc=tglx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox