From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/alternatives for 6.5
Date: Mon, 26 Jun 2023 15:01:24 +0200 [thread overview]
Message-ID: <20230626130124.GCZJmMJKLdnwrwkbzF@fat_crate.local> (raw)
Hi Linus,
please pull a bunch of x86 alternatives improvements for 6.5.
Thx.
---
The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_alternatives_for_v6.5
for you to fetch changes up to 2bd4aa9325821551648cf9738d6aa3a49317d7e5:
x86/alternative: PAUSE is not a NOP (2023-06-14 19:02:54 +0200)
----------------------------------------------------------------
- Up until now the Fast Short Rep Mov optimizations implied the presence
of the ERMS CPUID flag. AMD decoupled them with a BIOS setting so decouple
that dependency in the kernel code too
- Teach the alternatives machinery to handle relocations
- Make debug_alternative accept flags in order to see only that set of
patching done one is interested in
- Other fixes, cleanups and optimizations to the patching code
----------------------------------------------------------------
Borislav Petkov (AMD) (3):
x86/lib/memmove: Decouple ERMS from FSRM
x86/alternative: Optimize returns patching
x86/alternatives: Fix section mismatch warnings
Peter Zijlstra (7):
x86/alternative: Make debug-alternative selective
x86/alternative: Support relocations in alternatives
x86/alternative: Rewrite optimize_nops() some
x86/alternative: Complicate optimize_nops() some more
x86/alternatives: Add longer 64-bit NOPs
x86/nospec: Shorten RESET_CALL_DEPTH
x86/alternative: PAUSE is not a NOP
Steven Rostedt (Google) (1):
x86/alternatives: Add cond_resched() to text_poke_bp_batch()
arch/x86/include/asm/nops.h | 16 +-
arch/x86/include/asm/nospec-branch.h | 6 +-
arch/x86/kernel/alternative.c | 470 ++++++++++++++++++++++++-----------
arch/x86/lib/memmove_64.S | 13 +-
tools/arch/x86/include/asm/nops.h | 16 +-
tools/objtool/arch/x86/special.c | 8 +-
6 files changed, 361 insertions(+), 168 deletions(-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next reply other threads:[~2023-06-26 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 13:01 Borislav Petkov [this message]
2023-06-26 22:54 ` pr-tracker-bot
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=20230626130124.GCZJmMJKLdnwrwkbzF@fat_crate.local \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®