From: Zhen Lei <thunder.leizhen@huawei.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>,
Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Petr Mladek <pmladek@suse.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>, <bpf@vger.kernel.org>,
<linux-trace-kernel@vger.kernel.org>,
<live-patching@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Luis Chamberlain <mcgrof@kernel.org>,
<linux-modules@vger.kernel.org>
Cc: Zhen Lei <thunder.leizhen@huawei.com>
Subject: [PATCH 0/3] kallsyms: Optimize the search for module symbols by livepatch and bpf
Date: Fri, 30 Dec 2022 19:27:26 +0800 [thread overview]
Message-ID: <20221230112729.351-1-thunder.leizhen@huawei.com> (raw)
Patches 7-8 in [1] have been delayed until now due to merge conflicts. The
current patch 1/3 corresponds to patch 7/9 in [1], and the current patch 3/3
corresponds to patch 8/9 in [1]. But there are some changes. Originally, only
livepatch uses function module_kallsyms_on_each_symbol(), it find the specified
function for the specified module. Now, bpf also uses function
module_kallsyms_on_each_symbol(), it needs to traverse all the modules. So for
the new parameter 'modname' of module_kallsyms_on_each_symbol(), if it's NULL,
the symbols of all modules are still traversed for compatibility with the case
of bpf.
Patch 2/3 is new, as I understand it, it should be fine. If it doesn't work,
then patch 3/3 should be dropped.
[1] https://lkml.org/lkml/2022/11/2/225
Zhen Lei (3):
livepatch: Improve the search performance of
module_kallsyms_on_each_symbol()
bpf: Optimize get_modules_for_addrs()
kallsyms: Delete an unused parameter related to
{module_}kallsyms_on_each_symbol()
include/linux/kallsyms.h | 3 +-
include/linux/module.h | 8 +--
kernel/kallsyms.c | 5 +-
kernel/kallsyms_selftest.c | 6 +--
kernel/livepatch/core.c | 13 +----
kernel/module/kallsyms.c | 16 ++++--
kernel/trace/bpf_trace.c | 101 +++++++++++++++----------------------
kernel/trace/ftrace.c | 5 +-
8 files changed, 67 insertions(+), 90 deletions(-)
--
2.25.1
next reply other threads:[~2022-12-30 11:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 11:27 Zhen Lei [this message]
2022-12-30 11:27 ` [PATCH 1/3] livepatch: Improve the search performance of module_kallsyms_on_each_symbol() Zhen Lei
2023-01-04 15:36 ` Petr Mladek
2022-12-30 11:27 ` [PATCH 2/3] bpf: Optimize get_modules_for_addrs() Zhen Lei
2023-01-04 16:25 ` Petr Mladek
2023-01-04 17:07 ` Song Liu
2023-01-05 7:31 ` Leizhen (ThunderTown)
2023-01-05 9:05 ` Petr Mladek
2023-01-09 4:02 ` Leizhen (ThunderTown)
2023-01-05 7:48 ` Leizhen (ThunderTown)
2023-01-05 9:32 ` Petr Mladek
2023-01-09 4:10 ` Leizhen (ThunderTown)
2023-01-05 21:31 ` Jiri Olsa
2023-01-06 9:45 ` Jiri Olsa
2023-01-09 8:51 ` Leizhen (ThunderTown)
2023-01-09 13:48 ` Jiri Olsa
2023-01-09 15:11 ` Leizhen (ThunderTown)
2023-01-11 8:41 ` Leizhen (ThunderTown)
2023-01-11 9:53 ` Jiri Olsa
2023-01-09 7:03 ` Leizhen (ThunderTown)
2022-12-30 11:27 ` [PATCH 3/3] kallsyms: Delete an unused parameter related to {module_}kallsyms_on_each_symbol() Zhen Lei
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=20221230112729.351-1-thunder.leizhen@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=mbenes@suse.cz \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
/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;
as well as URLs for NNTP newsgroup(s).