From: Yonghong Song <yhs@fb.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Alan Maguire <alan.maguire@oracle.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Song Liu <songliubraving@fb.com>, Martin KaFai Lau <kafai@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Vernet <void@manifault.com>,
swboyd@chromium.org, Nick Desaulniers <ndesaulniers@google.com>,
Dmitrii Dolgov <9erthalion6@gmail.com>, Kenny Yu <kennyyu@fb.com>,
Geliang Tang <geliang.tang@suse.com>,
Kuniyuki Iwashima <kuniyu@amazon.co.jp>,
bpf <bpf@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 bpf-next 1/2] bpf: add a ksym BPF iterator
Date: Tue, 5 Jul 2022 23:12:02 -0700 [thread overview]
Message-ID: <3efda195-2d1a-2207-62c1-759a53ece20d@fb.com> (raw)
In-Reply-To: <CAADnVQKvtoBkCEBNcwKp1dp9_OPy9CtLD=QqscMQQJdoUf7OkQ@mail.gmail.com>
On 7/5/22 9:19 PM, Alexei Starovoitov wrote:
> On Mon, Jul 4, 2022 at 6:55 AM Alan Maguire <alan.maguire@oracle.com> wrote:
>> static inline int kallsyms_for_perf(void)
>> {
>> #ifdef CONFIG_PERF_EVENTS
>> @@ -885,6 +967,18 @@ const char *kdb_walk_kallsyms(loff_t *pos)
>> static int __init kallsyms_init(void)
>> {
>> proc_create("kallsyms", 0444, NULL, &kallsyms_proc_ops);
>> +#if defined(CONFIG_BPF_SYSCALL)
>> + {
>> + int ret;
>> +
>> + ksym_iter_reg_info.ctx_arg_info[0].btf_id = *btf_ksym_iter_id;
>> + ret = bpf_iter_reg_target(&ksym_iter_reg_info);
>> + if (ret) {
>> + pr_warn("Warning: could not register bpf ksym iterator: %d\n", ret);
>> + return ret;
>> + }
>> + }
>> +#endif
>
> The ifdef-s inside the function body are not pretty.
> I feel the v2 version was cleaner.
> static void __init bpf_ksym_iter_register()
> were only missing late_initcall(bpf_ksym_iter_register);
> to make it single #ifdef CONFIG_BPF_SYSCALL for everything.
> wdyt?
Okay, a separate function is good too. Also agree with Alexei
that a separate init call bpf_ksym_iter_register() is needed
since we need late_initcall(...) instead of device_initcall(...)
to be consistent with other bpf_iter's.
next prev parent reply other threads:[~2022-07-06 6:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 13:55 [PATCH v3 bpf-next 0/2] bpf: add a ksym BPF iterator Alan Maguire
2022-07-04 13:55 ` [PATCH v3 bpf-next 1/2] " Alan Maguire
2022-07-05 16:40 ` Yonghong Song
2022-07-06 4:19 ` Alexei Starovoitov
2022-07-06 6:12 ` Yonghong Song [this message]
2022-07-04 13:55 ` [PATCH v3 bpf-next 2/2] selftests/bpf: add a ksym iter subtest Alan Maguire
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=3efda195-2d1a-2207-62c1-759a53ece20d@fb.com \
--to=yhs@fb.com \
--cc=9erthalion6@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan.maguire@oracle.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=geliang.tang@suse.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kennyyu@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuniyu@amazon.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=ndesaulniers@google.com \
--cc=songliubraving@fb.com \
--cc=swboyd@chromium.org \
--cc=void@manifault.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