From: Leon Hwang <hffilwlqm@gmail.com>
To: Tao Chen <chen.dylane@linux.dev>,
ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
sdf@fomichev.me, haoluo@google.com, jolsa@kernel.org
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 2/2] selftests/bpf: Add stacktrace map lookup_and_delete_elem test case
Date: Mon, 22 Sep 2025 10:42:44 +0800 [thread overview]
Message-ID: <f1d2d0fc-c541-4acc-b5d6-34f2bba37aea@gmail.com> (raw)
In-Reply-To: <20250920155211.1354348-2-chen.dylane@linux.dev>
On 20/9/25 23:52, Tao Chen wrote:
> ...
> test_stacktrace_map:PASS:compare_stack_ips stackmap vs. stack_amap 0 nsec
> test_stacktrace_map:PASS:stack_key_map lookup 0 nsec
> test_stacktrace_map:PASS:stackmap lookup and detele 0 nsec
> test_stacktrace_map:PASS:stackmap lookup deleted stack_id 0 nsec
> #397 stacktrace_map:OK
> ...
As they suppose to pass, they are meaningless in the commit log.
Please describe what the test is for and what it is doing instead.
>
> Signed-off-by: Tao Chen <chen.dylane@linux.dev>
> ---
> .../selftests/bpf/prog_tests/stacktrace_map.c | 22 ++++++++++++++++++-
> .../selftests/bpf/progs/test_stacktrace_map.c | 8 +++++++
> 2 files changed, 29 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/bpf/prog_tests/stacktrace_map.c b/tools/testing/selftests/bpf/prog_tests/stacktrace_map.c
> index 84a7e405e91..7d38afe5cfc 100644
> --- a/tools/testing/selftests/bpf/prog_tests/stacktrace_map.c
> +++ b/tools/testing/selftests/bpf/prog_tests/stacktrace_map.c
> @@ -3,7 +3,7 @@
>
> void test_stacktrace_map(void)
> {
> - int control_map_fd, stackid_hmap_fd, stackmap_fd, stack_amap_fd;
> + int control_map_fd, stackid_hmap_fd, stackmap_fd, stack_amap_fd, stack_key_map_fd;
> const char *prog_name = "oncpu";
> int err, prog_fd, stack_trace_len;
> const char *file = "./test_stacktrace_map.bpf.o";
> @@ -11,6 +11,9 @@ void test_stacktrace_map(void)
> struct bpf_program *prog;
> struct bpf_object *obj;
> struct bpf_link *link;
> + __u32 stack_id;
> + char val_buf[PERF_MAX_STACK_DEPTH *
> + sizeof(struct bpf_stack_build_id)];
Nit: minor indentation issue here.
'val_buf' should stay on a single line, since up to 100 characters per
line are allowed.
NOTE: keep inverted Christmas tree style.
Thanks,
Leon
>
> err = bpf_prog_test_load(file, BPF_PROG_TYPE_TRACEPOINT, &obj, &prog_fd);
> if (CHECK(err, "prog_load", "err %d errno %d\n", err, errno))
> @@ -41,6 +44,10 @@ void test_stacktrace_map(void)
> if (CHECK_FAIL(stack_amap_fd < 0))
> goto disable_pmu;
>
> + stack_key_map_fd = bpf_find_map(__func__, obj, "stack_key_map");
> + if (CHECK_FAIL(stack_key_map_fd < 0))
> + goto disable_pmu;
> +
> /* give some time for bpf program run */
> sleep(1);
>
[...]
next prev parent reply other threads:[~2025-09-22 2:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-20 15:52 [PATCH bpf-next v3 1/2] bpf: Add lookup_and_delete_elem for BPF_MAP_STACK_TRACE Tao Chen
2025-09-20 15:52 ` [PATCH bpf-next v3 2/2] selftests/bpf: Add stacktrace map lookup_and_delete_elem test case Tao Chen
2025-09-22 2:42 ` Leon Hwang [this message]
2025-09-22 14:00 ` Tao Chen
2025-09-22 20:59 ` Andrii Nakryiko
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=f1d2d0fc-c541-4acc-b5d6-34f2bba37aea@gmail.com \
--to=hffilwlqm@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chen.dylane@linux.dev \
--cc=daniel@iogearbox.net \
--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=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--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
all inboxes | Powered by JetHome®