From: "Clément Léger" <cleger@rivosinc.com>
To: Paul Walmsley <pjw@kernel.org>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, hchauhan@ventanamicro.com,
apatel@ventanamicro.com, luxu.kernel@bytedance.com,
atishp@atishpatra.org, bjorn@rivosinc.com,
cuiyunhui@bytedance.com, 张展鹏 <zhangzhanpeng.jasper@bytedance.com>
Subject: Re: [PATCH v8 0/5] riscv: add support for SBI Supervisor Software Events
Date: Wed, 26 Nov 2025 07:38:57 +0100 [thread overview]
Message-ID: <4b22e7c4-4d3d-43b9-bc27-ffd7a86ad26a@rivosinc.com> (raw)
In-Reply-To: <350edd01-56ce-6558-1473-4b9231647e1e@kernel.org>
On 11/19/25 16:52, Paul Walmsley wrote:
>
> To add more context:
>
> On Wed, 19 Nov 2025, patchwork-bot+linux-riscv@kernel.org wrote:
>
>> This series was applied to riscv/linux.git (for-next)
>> by Paul Walmsley <pjw@kernel.org>:
>>
>> On Wed, 5 Nov 2025 08:26:32 +0000 you wrote:
>>> The SBI Supervisor Software Events (SSE) extensions provides a mechanism
>>> to inject software events from an SBI implementation to supervisor
>>> software such that it preempts all other supervisor level traps and
>>> interrupts. This extension is introduced by the SBI v3.0 specification[1].
>>>
>>> Various events are defined and can be send asynchronously to supervisor
>>> software (RAS, PMU, DEBUG, Asynchronous page fault) from SBI as well
>>> as platform specific events. Events can be either local (per-hart) or
>>> global. Events can be nested on top of each other based on priority and
>>> can interrupt the kernel at any time.
>>>
>>> [...]
>>
>> Here is the summary with links:
>> - [v8,1/5] riscv: add SBI SSE extension definitions
>> https://git.kernel.org/riscv/c/7bba38249b8a
>> - [v8,2/5] riscv: add support for SBI Supervisor Software Events extension
>> https://git.kernel.org/riscv/c/b52179e6de7d
>> - [v8,3/5] drivers: firmware: add riscv SSE support
>> https://git.kernel.org/riscv/c/5ffe60d26107
>> - [v8,4/5] perf: RISC-V: add support for SSE event
>> https://git.kernel.org/riscv/c/c6f3f04d2a9c
>> - [v8,5/5] selftests/riscv: add SSE test module
>> https://git.kernel.org/riscv/c/a123316660af
>
> This is a pretty sophisticated series. I was hoping to get more test
> reports on it and reviews (as Clément requested as well). In the meantime
> I've pulled them into for-next in the hopes that it might increase the
> number of potential testers. Am still very much interested in any test
> reports or additional reviews; if they come in this week, I'll consider
> rebuilding for-next to add them.
Hey Paul,
Since we gathered additional bug/starvation reports with SSE from
Zhanpeng, it would be preferable to remove this series from your branch
if still possible. I'm not currently really available (just had a
newborn) so I won't be able to fix this quickly.
Thanks,
Clément
>
>
> - Paul
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-11-26 6:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 8:26 [PATCH v8 0/5] riscv: add support for SBI Supervisor Software Events Clément Léger
2025-11-05 8:26 ` [PATCH v8 1/5] riscv: add SBI SSE extension definitions Clément Léger
2025-11-05 8:26 ` [PATCH v8 2/5] riscv: add support for SBI Supervisor Software Events extension Clément Léger
2025-11-05 8:26 ` [PATCH v8 3/5] drivers: firmware: add riscv SSE support Clément Léger
2026-03-04 2:14 ` Jimmy Ho
2025-11-05 8:26 ` [PATCH v8 4/5] perf: RISC-V: add support for SSE event Clément Léger
2025-12-12 3:16 ` [External] " yunhui cui
2025-12-16 20:36 ` Clément Léger
2025-12-17 2:22 ` yunhui cui
2025-12-28 13:50 ` Clément Léger
2025-11-05 8:26 ` [PATCH v8 5/5] selftests/riscv: add SSE test module Clément Léger
2025-11-19 12:30 ` [PATCH v8 0/5] riscv: add support for SBI Supervisor Software Events patchwork-bot+linux-riscv
2025-11-19 15:52 ` Paul Walmsley
2025-11-26 6:38 ` Clément Léger [this message]
2025-11-26 20:00 ` Paul Walmsley
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=4b22e7c4-4d3d-43b9-bc27-ffd7a86ad26a@rivosinc.com \
--to=cleger@rivosinc.com \
--cc=apatel@ventanamicro.com \
--cc=atishp@atishpatra.org \
--cc=bjorn@rivosinc.com \
--cc=cuiyunhui@bytedance.com \
--cc=hchauhan@ventanamicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luxu.kernel@bytedance.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pjw@kernel.org \
--cc=zhangzhanpeng.jasper@bytedance.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