From: "Alexis Lothoré" <alexis.lothore@bootlin.com>
To: Alan Maguire <alan.maguire@oracle.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Mykola Lysenko <mykolal@fb.com>,
Shuah Khan <shuah@kernel.org>
Cc: ebpf@linuxfoundation.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next 1/4] selftests/bpf: convert get_current_cgroup_id_user to test_progs
Date: Wed, 31 Jul 2024 20:53:21 +0200 [thread overview]
Message-ID: <f60d47cc-84ff-4031-a9e6-244954af901e@bootlin.com> (raw)
In-Reply-To: <f54ddf95-a5ab-4c56-966f-9bff37f50364@oracle.com>
Hello Alan,
On 7/31/24 19:23, Alan Maguire wrote:
> On 31/07/2024 11:38, Alexis Lothoré (eBPF Foundation) wrote:
[...]
>> + pid = getpid();
>> + if (!ASSERT_OK(bpf_map__update_elem(skel->maps.pidmap, &key,
>> + sizeof(key), &pid, sizeof(pid), 0),
>> + "write pid"))
>> + goto cleanup_progs;
>> +
>
> I think it would be worth using a global variable in the BPF program
> my_pid, and setting skel->bss->my_pid here as other more up-to-date
> tests do (example progs/test_usdt.c, prog_tests/usdt.c). No need for a
> separate map anymore.
That sounds like a good improvement, thanks for the hint and the example :) I'll
spin a new revision with this, and make sure to use it in my next test
conversion patches too when relevant.
TBH I am not familiar with global variables usage in ebpf/libbpf, so it is not
clear for me when I should prefer it over classic maps. From some quick search I
feel like it should be the default choice when needing basic controls
knobs/feedback on a bpf program from userspace ? Or maybe it should be used even
more broadly by default ?
>> + /* trigger the syscall on which is attached the tested prog */
>> + if (!ASSERT_OK(syscall(__NR_nanosleep, &req, NULL), "nanosleep"))
>> + goto cleanup_progs;
>> +
>> + if (!ASSERT_OK(bpf_map__lookup_elem(skel->maps.cg_ids, &key,
>> + sizeof(key), &kcgid, sizeof(kcgid),
>> + 0),
>> + "read bpf cgroup id"))
>> + goto cleanup_progs;
>> +
>
> ditto here, cg_ids could be a global var cg_id that the bpf prog sets
> and we check here via skel->bss->cg_id.
ACK, I'll update this too.
Thanks,
Alexis
--
Alexis Lothoré, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-07-31 18:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 10:38 [PATCH bpf-next 0/4] selftests/bpf: convert three other cgroup tests to test_progs Alexis Lothoré (eBPF Foundation)
2024-07-31 10:38 ` [PATCH bpf-next 1/4] selftests/bpf: convert get_current_cgroup_id_user " Alexis Lothoré (eBPF Foundation)
2024-07-31 17:23 ` Alan Maguire
2024-07-31 18:53 ` Alexis Lothoré [this message]
2024-08-01 8:17 ` Alan Maguire
2024-08-01 8:57 ` Alexis Lothoré
2024-07-31 10:38 ` [PATCH bpf-next 2/4] selftests/bpf: convert test_cgroup_storage " Alexis Lothoré (eBPF Foundation)
2024-08-01 8:27 ` Alan Maguire
2024-08-01 9:21 ` Alexis Lothoré
2024-08-06 12:38 ` Alan Maguire
2024-07-31 10:38 ` [PATCH bpf-next 3/4] selftests/bpf: add proper section name to bpf prog and rename it Alexis Lothoré (eBPF Foundation)
2024-08-01 8:35 ` Alan Maguire
2024-08-01 10:00 ` Alexis Lothoré
2024-08-06 12:33 ` Alan Maguire
2024-08-06 17:24 ` Alexis Lothoré
2024-07-31 10:38 ` [PATCH bpf-next 4/4] selftests/bpf: convert test_skb_cgroup_id_user to test_progs Alexis Lothoré (eBPF Foundation)
2024-08-01 8:49 ` Alan Maguire
2024-08-01 10:12 ` Alexis Lothoré
2024-08-06 12:26 ` 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=f60d47cc-84ff-4031-a9e6-244954af901e@bootlin.com \
--to=alexis.lothore@bootlin.com \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=ebpf@linuxfoundation.org \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yonghong.song@linux.dev \
/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