From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org,
kuniyu@amazon.com, kafai@fb.com
Subject: Re: [PATCH bpf-next v4 1/2] bpf: Track aligned st store as imprecise spilled registers
Date: Fri, 12 Jan 2024 20:30:25 +0000 [thread overview]
Message-ID: <170509142565.8964.750077660588376018.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240110051348.2737007-1-yonghong.song@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 9 Jan 2024 21:13:48 -0800 you wrote:
> With patch set [1], precision backtracing supports register spill/fill
> to/from the stack. The patch [2] allows initial imprecise register spill
> with content 0. This is a common case for cpuv3 and lower for
> initializing the stack variables with pattern
> r1 = 0
> *(u64 *)(r10 - 8) = r1
> and the [2] has demonstrated good verification improvement.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/2] bpf: Track aligned st store as imprecise spilled registers
https://git.kernel.org/bpf/bpf-next/c/17e25d8e59f2
- [bpf-next,v4,2/2] selftests/bpf: Add a selftest with not-8-byte aligned BPF_ST
https://git.kernel.org/bpf/bpf-next/c/536dfcbad359
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:[~2024-01-12 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 5:13 [PATCH bpf-next v4 1/2] bpf: Track aligned st store as imprecise spilled registers Yonghong Song
2024-01-10 5:13 ` [PATCH bpf-next v4 2/2] selftests/bpf: Add a selftest with not-8-byte aligned BPF_ST Yonghong Song
2024-01-10 17:54 ` [PATCH bpf-next v4 1/2] bpf: Track aligned st store as imprecise spilled registers Kuniyuki Iwashima
2024-01-12 20:05 ` Andrii Nakryiko
2024-01-12 20:30 ` 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=170509142565.8964.750077660588376018.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=kafai@fb.com \
--cc=kernel-team@fb.com \
--cc=kuniyu@amazon.com \
--cc=martin.lau@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