From: Jiri Olsa <olsajiri@gmail.com>
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
yonghong.song@linux.dev
Subject: Re: [PATCH RFC bpf-next v3 4/6] bpf: report hot simulated callchains when 1M instructions limit is met
Date: Fri, 29 May 2026 12:23:31 +0200 [thread overview]
Message-ID: <ahlpI7sRJt1FQdYg@krava> (raw)
In-Reply-To: <20260527-better-1m-reporting-v3-4-b3ede0588a75@gmail.com>
On Wed, May 27, 2026 at 12:29:52AM -0700, Eduard Zingerman wrote:
SNIP
> +
> static int do_check_insn(struct bpf_verifier_env *env, bool *do_print_state)
> {
> int err;
> @@ -17381,6 +17527,7 @@ static int do_check(struct bpf_verifier_env *env)
> insn_aux = &env->insn_aux_data[env->insn_idx];
>
> if (++env->insn_processed > BPF_COMPLEXITY_LIMIT_INSNS) {
> + print_hotspots(env);
hi,
this is really cool feature, I've already used it to fix issues :)
Would it be possible to make this configurable? like to be able
to get this output for program that passed and display more than
3 hottest callchains?
thanks,
jirka
> verbose(env,
> "BPF program is too large. Processed %d insn\n",
> env->insn_processed);
> @@ -17390,6 +17537,12 @@ static int do_check(struct bpf_verifier_env *env)
> state->last_insn_idx = env->prev_insn_idx;
> state->insn_idx = env->insn_idx;
>
> + if (bpf_is_force_checkpoint(env, env->insn_idx) || insn_aux->loop) {
> + err = update_callchain_profile(env, state);
> + if (err)
> + return err;
> + }
> +
> if (bpf_is_prune_point(env, env->insn_idx)) {
> err = bpf_is_state_visited(env, env->insn_idx);
> if (err < 0)
> @@ -19673,6 +19826,7 @@ int bpf_check(struct bpf_prog **prog, union bpf_attr *attr, bpfptr_t uattr,
> return -ENOMEM;
>
> env->bt.env = env;
> + hash_init(env->callchain_htab);
>
> len = (*prog)->len;
> env->insn_aux_data =
> @@ -19945,6 +20099,7 @@ int bpf_check(struct bpf_prog **prog, union bpf_attr *attr, bpfptr_t uattr,
> bpf_clear_insn_aux_data(env, 0, env->prog->len);
> vfree(env->insn_aux_data);
> err_free_env:
> + free_callchain_profile(env);
> bpf_stack_liveness_free(env);
> kvfree(env->cfg.insn_postorder);
> kvfree(env->scc_info);
>
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-05-29 10:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 7:29 [PATCH RFC bpf-next v3 0/6] bpf: better error reporting when verifier hits 1M instructions limit Eduard Zingerman
2026-05-27 7:29 ` [PATCH RFC bpf-next v3 1/6] bpf: move live registers and scc printout to a standalone function Eduard Zingerman
2026-06-01 5:50 ` Emil Tsalapatis
2026-05-27 7:29 ` [PATCH RFC bpf-next v3 2/6] bpf: compute loops hierarchy Eduard Zingerman
2026-06-01 19:12 ` Emil Tsalapatis
2026-06-01 19:22 ` Eduard Zingerman
2026-06-01 19:29 ` Emil Tsalapatis
2026-05-27 7:29 ` [PATCH RFC bpf-next v3 3/6] selftests/bpf: test cases for loop hierarchy computation Eduard Zingerman
2026-05-27 8:50 ` sashiko-bot
2026-06-01 19:37 ` Emil Tsalapatis
2026-06-01 19:44 ` Eduard Zingerman
2026-05-27 7:29 ` [PATCH RFC bpf-next v3 4/6] bpf: report hot simulated callchains when 1M instructions limit is met Eduard Zingerman
2026-05-29 10:23 ` Jiri Olsa [this message]
2026-05-29 18:44 ` Eduard Zingerman
2026-05-30 9:34 ` Jiri Olsa
2026-06-01 19:50 ` Emil Tsalapatis
2026-06-01 19:55 ` Eduard Zingerman
2026-05-27 7:29 ` [PATCH RFC bpf-next v3 5/6] bpf: report register diff summary for hot callchains Eduard Zingerman
2026-06-01 21:29 ` Emil Tsalapatis
2026-06-01 21:38 ` Eduard Zingerman
2026-05-27 7:29 ` [PATCH RFC bpf-next v3 6/6] selftests/bpf: test budget exhaustion profiling report Eduard Zingerman
2026-06-01 19:55 ` Emil Tsalapatis
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=ahlpI7sRJt1FQdYg@krava \
--to=olsajiri@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--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