From: patchwork-bot+netdevbpf@kernel.org
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: andrii@kernel.org, eddyz87@gmail.com, ihor.solodrai@linux.dev,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v1] selftests/bpf: Add get_preempt_count() support for RISC-V
Date: Fri, 24 Jul 2026 21:00:09 +0000 [thread overview]
Message-ID: <178492680940.3305171.3051143436591504393.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260722022906.8778-1-yangtiezhu@loongson.cn>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Wed, 22 Jul 2026 10:29:06 +0800 you wrote:
> Currently, there is no RISC-V support for get_preempt_count() and
> its fallback path always returns 0.
>
> Add it so that bpf_in_interrupt(), bpf_in_nmi(), bpf_in_hardirq(),
> bpf_in_serving_softirq(), and bpf_in_task() work for RISC-V as well.
>
> Given that RISC-V has supported CONFIG_THREAD_INFO_IN_TASK since its
> initial commit fbe934d69eb7 ("RISC-V: Build Infrastructure") in 2017,
> directly retrieve preempt_count from the thread_info embedded within
> task_struct via bpf_get_current_task_btf().
>
> [...]
Here is the summary with links:
- [bpf-next,v1] selftests/bpf: Add get_preempt_count() support for RISC-V
https://git.kernel.org/bpf/bpf-next/c/9b19237a46e7
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:[~2026-07-24 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 2:29 Tiezhu Yang
2026-07-22 2:51 ` Pu Lehui
2026-07-24 21:00 ` 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=178492680940.3305171.3051143436591504393.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=yangtiezhu@loongson.cn \
/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
all inboxes | Powered by JetHome®