From: Petr Pavlu <petr.pavlu@suse.com>
To: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, hpa@zytor.com, mhiramat@kernel.org
Cc: peterz@infradead.org, samitolvanen@google.com, x86@kernel.org,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
Petr Pavlu <petr.pavlu@suse.com>
Subject: [PATCH 0/2] x86/retpoline,kprobes: Fix the [__indirect_thunk_start, ..end] range
Date: Wed, 5 Jul 2023 10:15:45 +0200 [thread overview]
Message-ID: <20230705081547.25130-1-petr.pavlu@suse.com> (raw)
Fix problems with an output position of thunk sections and the
associated definition of range [__indirect_thunk_start,
__indirect_thunk_end] which affects the kprobes optimization.
Petr Pavlu (2):
x86/retpoline,kprobes: Fix position of thunk sections with
CONFIG_LTO_CLANG
x86/retpoline,kprobes: Avoid treating rethunk as an indirect jump
arch/x86/kernel/vmlinux.lds.S | 4 +---
arch/x86/lib/retpoline.S | 8 ++++++--
2 files changed, 7 insertions(+), 5 deletions(-)
--
2.35.3
next reply other threads:[~2023-07-05 8:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 8:15 Petr Pavlu [this message]
2023-07-05 8:15 ` [PATCH 1/2] x86/retpoline,kprobes: Fix position of thunk sections with CONFIG_LTO_CLANG Petr Pavlu
2023-07-05 8:52 ` Peter Zijlstra
2023-07-05 8:15 ` [PATCH 2/2] x86/retpoline,kprobes: Avoid treating rethunk as an indirect jump Petr Pavlu
2023-07-05 8:58 ` Peter Zijlstra
2023-07-05 14:20 ` Masami Hiramatsu
2023-07-05 14:50 ` Peter Zijlstra
2023-07-06 0:47 ` Masami Hiramatsu
2023-07-06 7:17 ` Peter Zijlstra
2023-07-06 9:00 ` Masami Hiramatsu
2023-07-06 11:34 ` Peter Zijlstra
2023-07-07 14:39 ` Masami Hiramatsu
2023-07-08 14:18 ` Petr Pavlu
2023-07-09 15:25 ` Masami Hiramatsu
2023-07-05 9:02 ` Peter Zijlstra
2023-07-05 14:40 ` Masami Hiramatsu
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=20230705081547.25130-1-petr.pavlu@suse.com \
--to=petr.pavlu@suse.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=samitolvanen@google.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
all inboxes | Powered by JetHome®