From: patchwork-bot+netdevbpf@kernel.org
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, tj@kernel.org
Subject: Re: [PATCH bpf-next v3 0/5] bpf: simple DFA-based live registers analysis
Date: Tue, 04 Mar 2025 21:10:34 +0000 [thread overview]
Message-ID: <174112263451.294592.2291982366290755107.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250304195024.2478889-1-eddyz87@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 4 Mar 2025 11:50:19 -0800 you wrote:
> This patch-set introduces a simple live registers DFA analysis.
> Analysis is done as a separate step before main verification pass.
> Results are stored in the env->insn_aux_data for each instruction.
>
> The change helps with iterator/callback based loops handling,
> as regular register liveness marks are not finalized while
> loops are processed. See veristat results in patch #2.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/5] bpf: jmp_offset() and verbose_insn() utility functions
https://git.kernel.org/bpf/bpf-next/c/1c152572be59
- [bpf-next,v3,2/5] bpf: get_call_summary() utility function
https://git.kernel.org/bpf/bpf-next/c/0ae958eca164
- [bpf-next,v3,3/5] bpf: simple DFA-based live registers analysis
https://git.kernel.org/bpf/bpf-next/c/7dad03653567
- [bpf-next,v3,4/5] bpf: use register liveness information for func_states_equal
https://git.kernel.org/bpf/bpf-next/c/994a876a076a
- [bpf-next,v3,5/5] selftests/bpf: test cases for compute_live_registers()
https://git.kernel.org/bpf/bpf-next/c/8a3fc22ddec7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-03-04 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 19:50 [PATCH bpf-next v3 0/5] bpf: simple DFA-based live registers analysis Eduard Zingerman
2025-03-04 19:50 ` [PATCH bpf-next v3 1/5] bpf: jmp_offset() and verbose_insn() utility functions Eduard Zingerman
2025-03-04 19:50 ` [PATCH bpf-next v3 2/5] bpf: get_call_summary() utility function Eduard Zingerman
2025-03-04 19:50 ` [PATCH bpf-next v3 3/5] bpf: simple DFA-based live registers analysis Eduard Zingerman
2025-03-04 19:50 ` [PATCH bpf-next v3 4/5] bpf: use register liveness information for func_states_equal Eduard Zingerman
2025-03-04 19:50 ` [PATCH bpf-next v3 5/5] selftests/bpf: test cases for compute_live_registers() Eduard Zingerman
2025-03-04 21:10 ` patchwork-bot+netdevbpf [this message]
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=174112263451.294592.2291982366290755107.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=tj@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