From: Masami Hiramatsu <mhiramat@kernel.org>
To: Jiri Olsa <jolsa@kernel.org>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
lkml <linux-kernel@vger.kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@chromium.org>
Subject: Re: [PATCHv2 bpf-next 2/4] fprobe: Resolve symbols with kallsyms_lookup_names
Date: Mon, 18 Apr 2022 23:39:54 +0900 [thread overview]
Message-ID: <20220418233954.0b17b003759d54b81e78888b@kernel.org> (raw)
In-Reply-To: <20220418124834.829064-3-jolsa@kernel.org>
Hi Jiri,
On Mon, 18 Apr 2022 14:48:32 +0200
Jiri Olsa <jolsa@kernel.org> wrote:
> Using kallsyms_lookup_names to speed up symbols lookup
> in register_fprobe_syms API.
>
> This requires syms array to be alphabetically sorted.
This looks good to me. But we may need to update this for changing
the function name "kallsyms_lookup_names()". I think "ftrace_lookup_sorted_syms()"
will be better to understand.
What would you think?
Thank you,
>
> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> ---
> kernel/trace/fprobe.c | 32 ++++++++++++--------------------
> 1 file changed, 12 insertions(+), 20 deletions(-)
>
> diff --git a/kernel/trace/fprobe.c b/kernel/trace/fprobe.c
> index 89d9f994ebb0..6419501a0036 100644
> --- a/kernel/trace/fprobe.c
> +++ b/kernel/trace/fprobe.c
> @@ -85,39 +85,31 @@ static void fprobe_exit_handler(struct rethook_node *rh, void *data,
> }
> NOKPROBE_SYMBOL(fprobe_exit_handler);
>
> +static int symbols_cmp(const void *a, const void *b)
> +{
> + const char **str_a = (const char **) a;
> + const char **str_b = (const char **) b;
> +
> + return strcmp(*str_a, *str_b);
> +}
> +
> /* Convert ftrace location address from symbols */
> static unsigned long *get_ftrace_locations(const char **syms, int num)
> {
> - unsigned long addr, size;
> unsigned long *addrs;
> - int i;
>
> /* Convert symbols to symbol address */
> addrs = kcalloc(num, sizeof(*addrs), GFP_KERNEL);
> if (!addrs)
> return ERR_PTR(-ENOMEM);
>
> - for (i = 0; i < num; i++) {
> - addr = kallsyms_lookup_name(syms[i]);
> - if (!addr) /* Maybe wrong symbol */
> - goto error;
> -
> - /* Convert symbol address to ftrace location. */
> - if (!kallsyms_lookup_size_offset(addr, &size, NULL) || !size)
> - goto error;
> + /* kallsyms_lookup_names expects sorted symbols */
> + sort(syms, num, sizeof(*syms), symbols_cmp, NULL);
>
> - addr = ftrace_location_range(addr, addr + size - 1);
> - if (!addr) /* No dynamic ftrace there. */
> - goto error;
> + if (!kallsyms_lookup_names(syms, num, addrs))
> + return addrs;
>
> - addrs[i] = addr;
> - }
> -
> - return addrs;
> -
> -error:
> kfree(addrs);
> -
> return ERR_PTR(-ENOENT);
> }
>
> --
> 2.35.1
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2022-04-18 15:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 12:48 [PATCHv2 bpf-next 0/4] bpf: Speed up symbol resolving in kprobe multi link Jiri Olsa
2022-04-18 12:48 ` [PATCHv2 bpf-next 1/4] kallsyms: Add kallsyms_lookup_names function Jiri Olsa
2022-04-18 14:35 ` Masami Hiramatsu
2022-04-19 8:26 ` Jiri Olsa
2022-04-22 6:47 ` Jiri Olsa
2022-04-26 10:01 ` Masami Hiramatsu
2022-04-26 12:27 ` Jiri Olsa
2022-04-26 16:03 ` Masami Hiramatsu
2022-04-18 12:48 ` [PATCHv2 bpf-next 2/4] fprobe: Resolve symbols with kallsyms_lookup_names Jiri Olsa
2022-04-18 14:39 ` Masami Hiramatsu [this message]
2022-04-18 12:48 ` [PATCHv2 bpf-next 3/4] bpf: Resolve symbols with kallsyms_lookup_names for kprobe multi link Jiri Olsa
2022-04-20 21:49 ` Andrii Nakryiko
2022-04-21 6:49 ` Jiri Olsa
2022-04-18 12:48 ` [PATCHv2 bpf-next 4/4] selftests/bpf: Add attach bench test Jiri Olsa
2022-04-20 21:56 ` Andrii Nakryiko
2022-04-21 6:56 ` Jiri Olsa
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=20220418233954.0b17b003759d54b81e78888b@kernel.org \
--to=mhiramat@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--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).