From: Charlie Jenkins <thecharlesjenkins@gmail.com>
To: Himanshu Chauhan <himanshu.chauhan@oss.qualcomm.com>
Cc: opensbi@lists.infradead.org, weidongwd <weidong.wd@bytedance.com>
Subject: Re: [PATCH] lib: sbi: Use SBI_SSE_EVENT_LOCAL_UNKNOWN_NMI with unknown interrupts
Date: Wed, 25 Feb 2026 16:37:40 -0800 [thread overview]
Message-ID: <20260226003740.GA538838@charlie> (raw)
In-Reply-To: <CA+Ht8=YMejcSnkA+8ODbzD0pUYaDbh0YkmqLmq1FiQEY_R=nBA@mail.gmail.com>
On Thu, Feb 19, 2026 at 12:23:23PM +0530, Himanshu Chauhan wrote:
> Hi,
>
> On Wed, Feb 18, 2026 at 7:58 AM Charlie Jenkins via B4 Relay
> <devnull+thecharlesjenkins.gmail.com@kernel.org> wrote:
> >
> > From: Charlie Jenkins <thecharlesjenkins@gmail.com>
> >
> > An mcause of 0 means "unknown cause" according to the riscv privileged
> > spec. When this occurs, the interrupt should be forwarded to S-mode
> > software via SBI_SSE_EVENT_GLOBAL_UNKNOWN_NMI if SSE is enabled.
> >
>
> This is an incorrect interpretation of the spec. The specification has
> "reserved" the mcause exception code 0 of interrupts.
> IMHO, a reserved interrupt, if occurs, shouldn't be forwarded to
> supervisor software.
Yeah that was a misinformed interpretation, thank you for your feedback.
- Charlie
>
> Regards
> Himanshu
>
> --
> opensbi mailing list
> opensbi@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/opensbi
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
prev parent reply other threads:[~2026-02-26 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 2:26 [PATCH] lib: sbi: Use SBI_SSE_EVENT_LOCAL_UNKNOWN_NMI with unknown interrupts Charlie Jenkins via B4 Relay
2026-02-19 6:53 ` Himanshu Chauhan
2026-02-26 0:37 ` Charlie Jenkins [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=20260226003740.GA538838@charlie \
--to=thecharlesjenkins@gmail.com \
--cc=himanshu.chauhan@oss.qualcomm.com \
--cc=opensbi@lists.infradead.org \
--cc=weidong.wd@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