From: sashiko-bot@kernel.org
To: "Andrii Nakryiko" <andrii@kernel.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH bpf-next 2/3] selftests/bpf: Add stacktrace_ips test for tracepoint
Date: Sat, 14 Nov 2026 00:26:21 +0000 [thread overview]
Message-ID: <sashiko-outbox-213921@kernel.org> (raw)
In-Reply-To: <20261114001846.873499-3-andrii@kernel.org>
> Add a tp subtest that checks the stack captured by bpf_get_stack()
> from a tracepoint program, recorded only for the test's own process.
> Depending on static calls and inlining, the stack may or may not have
> __traceiter_bpf_testmod_test_read in front of bpf_testmod_test_read,
> so accept both. Also check that the entry after it differs: kernels
> without commit 6d08340d1e35 ("Revert "perf/x86: Always store regs->ip
> in perf_callchain_kernel()"") report the tracepoint's caller twice.
>
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261114001846.873499-1-andrii@kernel.org?part=2
next prev parent reply other threads:[~2026-11-14 0:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 0:18 [PATCH bpf-next 0/3] Fix duplicate caller frame in arm64 stack traces Andrii Nakryiko
2026-11-14 0:18 ` [PATCH bpf-next 1/3] arm64: perf: Don't report the caller twice in caller-regs callchains Andrii Nakryiko
2026-11-14 0:26 ` sashiko-bot
2026-11-14 0:18 ` [PATCH bpf-next 2/3] selftests/bpf: Add stacktrace_ips test for tracepoint Andrii Nakryiko
2026-11-14 0:26 ` sashiko-bot [this message]
2026-11-14 0:18 ` [PATCH bpf-next 3/3] selftests/bpf: Run stacktrace_ips raw_tp, tp and fentry tests on arm64 Andrii Nakryiko
2026-11-14 0:30 ` sashiko-bot
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=sashiko-outbox-213921@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=andrii@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.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