From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, kkd@meta.com, ast@kernel.org,
andrii@kernel.org, daniel@iogearbox.net, martin.lau@kernel.org,
eddyz87@gmail.com, kernel-team@fb.com
Subject: Re: [PATCH bpf-next v6 0/7] IRQ save/restore
Date: Wed, 04 Dec 2024 16:50:34 +0000 [thread overview]
Message-ID: <173333103407.1261085.15986829219846341808.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241204030400.208005-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 3 Dec 2024 19:03:53 -0800 you wrote:
> This set introduces support for managing IRQ state from BPF programs.
> Two new kfuncs, bpf_local_irq_save, and bpf_local_irq_restore are
> introduced to enable this functionality.
>
> Intended use cases are writing IRQ safe data structures (e.g. memory
> allocator) in BPF programs natively, and use in new spin locking
> primitives intended to be introduced in the next few weeks.
>
> [...]
Here is the summary with links:
- [bpf-next,v6,1/7] bpf: Consolidate locks and reference state in verifier state
https://git.kernel.org/bpf/bpf-next/c/1995edc5f908
- [bpf-next,v6,2/7] bpf: Refactor {acquire,release}_reference_state
https://git.kernel.org/bpf/bpf-next/c/769b0f1c8214
- [bpf-next,v6,3/7] bpf: Refactor mark_{dynptr,iter}_read
https://git.kernel.org/bpf/bpf-next/c/b79f5f54e1dc
- [bpf-next,v6,4/7] bpf: Introduce support for bpf_local_irq_{save,restore}
https://git.kernel.org/bpf/bpf-next/c/c8e2ee1f3df0
- [bpf-next,v6,5/7] bpf: Improve verifier log for resource leak on exit
https://git.kernel.org/bpf/bpf-next/c/cbd8730aea8d
- [bpf-next,v6,6/7] selftests/bpf: Expand coverage of preempt tests to sleepable kfunc
https://git.kernel.org/bpf/bpf-next/c/e8c6c80b76e5
- [bpf-next,v6,7/7] selftests/bpf: Add IRQ save/restore tests
https://git.kernel.org/bpf/bpf-next/c/4fec4c22f046
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-12-04 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 3:03 [PATCH bpf-next v6 0/7] IRQ save/restore Kumar Kartikeya Dwivedi
2024-12-04 3:03 ` [PATCH bpf-next v6 1/7] bpf: Consolidate locks and reference state in verifier state Kumar Kartikeya Dwivedi
2024-12-04 3:03 ` [PATCH bpf-next v6 2/7] bpf: Refactor {acquire,release}_reference_state Kumar Kartikeya Dwivedi
2024-12-04 3:03 ` [PATCH bpf-next v6 3/7] bpf: Refactor mark_{dynptr,iter}_read Kumar Kartikeya Dwivedi
2024-12-04 3:03 ` [PATCH bpf-next v6 4/7] bpf: Introduce support for bpf_local_irq_{save,restore} Kumar Kartikeya Dwivedi
2024-12-04 3:03 ` [PATCH bpf-next v6 5/7] bpf: Improve verifier log for resource leak on exit Kumar Kartikeya Dwivedi
2024-12-04 3:03 ` [PATCH bpf-next v6 6/7] selftests/bpf: Expand coverage of preempt tests to sleepable kfunc Kumar Kartikeya Dwivedi
2024-12-04 3:04 ` [PATCH bpf-next v6 7/7] selftests/bpf: Add IRQ save/restore tests Kumar Kartikeya Dwivedi
2024-12-04 16:50 ` 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=173333103407.1261085.15986829219846341808.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=kkd@meta.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
/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