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 v6.3-rc1
Date: Mon, 20 Feb 2023 16:23:45 +0100 [thread overview]
Message-ID: <Y/OQgYnbYg0OzUMX@zn.tnic> (raw)
Hi Linus,
please pull some x86 alternatives improvements for 6.3.
Thx.
---
The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:
Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_alternatives_for_v6.3_rc1
for you to fetch changes up to 923510c88d2b7d947c4217835fd9ca6bd65cc56c:
x86/static_call: Add support for Jcc tail-calls (2023-01-31 15:05:31 +0100)
----------------------------------------------------------------
- Teach the static_call patching infrastructure to handle conditional
tall calls properly which can be static calls too
- Add proper struct alt_instr.flags which controls different aspects of
insn patching behavior
----------------------------------------------------------------
Borislav Petkov (AMD) (1):
x86/alternatives: Add alt_instr.flags
Peter Zijlstra (3):
x86/alternatives: Introduce int3_emulate_jcc()
x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions
x86/static_call: Add support for Jcc tail-calls
arch/x86/include/asm/alternative.h | 132 +++++++++++++++-----------
arch/x86/include/asm/text-patching.h | 31 ++++++
arch/x86/kernel/alternative.c | 76 ++++++++++-----
arch/x86/kernel/kprobes/core.c | 38 ++------
arch/x86/kernel/static_call.c | 50 +++++++++-
tools/objtool/arch/x86/include/arch/special.h | 6 +-
6 files changed, 218 insertions(+), 115 deletions(-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next reply other threads:[~2023-02-20 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 15:23 Borislav Petkov [this message]
2023-02-21 17:24 ` 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=Y/OQgYnbYg0OzUMX@zn.tnic \
--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®