From: Paul Walmsley <pjw@kernel.org>
To: Radim Krcmar <rkrcmar@qti.qualcomm.com>
Cc: "Paul Walmsley" <pjw@kernel.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
"Atish Patra" <atishp@rivosinc.com>,
"ajones@ventanamicro.com" <ajones@ventanamicro.com>,
"Clément Léger" <cleger@rivosinc.com>,
"apatel@ventanamicro.com" <apatel@ventanamicro.com>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"David Laight" <david.laight.linux@gmail.com>,
linux-riscv <linux-riscv-bounces@lists.infradead.org>
Subject: Re: [PATCH v2 2/2] RISC-V: make use of variadic sbi_ecall
Date: Wed, 7 Oct 2026 20:46:57 -0600 (MDT) [thread overview]
Message-ID: <d94ecb9c-def7-a9cb-456b-60b18489d0f3@kernel.org> (raw)
In-Reply-To: <DLYI0I8PT4LZ.ZSXV160QVO0H@qti.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
On Wed, 7 Oct 2026, Radim Krcmar wrote:
> 2026-10-06T03:55:12-06:00, Paul Walmsley <pjw@kernel.org>:
> > On Thu, 19 Jun 2025, Radim Krčmář wrote:
> >
> >> The new sbi_ecall doesn't have to list all 8 arguments anymore, so only
> >> pass the actual numbers of arguments for each SBI function.
> >>
> >> The remaining trailing 0 are intentional as they represent an argument.
> >>
> >> SBI 0.1 shouldn't be using the sbi_ecall, because it's only for 0.2+,
> >> but allow it by passing 0 is the reserved register.
> >>
> >> Signed-off-by: Radim Krčmář <rkrcmar@ventanamicro.com>
> >
> > Thanks, queued for v7.4.
> >
> > For everyone, not just Radim - probably it's worth looking through the
> > codebase to convert any SBI ecalls that were added over the past year that
> > weren't covered by this patch (e.g., the MPXY drivers) and to doublecheck
> > the overall argument counts.
>
> I started working on a followup and noticed a bug.
>
> Please squash the following change or just drop the second patch, since
> we may be touching the same lines again soon, sorry about that.
Thanks, squashed in.
- Paul
next prev parent reply other threads:[~2026-10-08 2:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 19:03 [PATCH v2 0/2] RISC-V: turn sbi_ecall into a variadic macro Radim Krčmář
2025-06-19 19:03 ` [PATCH v2 1/2] RISC-V: sbi: turn sbi_ecall into " Radim Krčmář
2026-10-06 9:47 ` Paul Walmsley
2025-06-19 19:03 ` [PATCH v2 2/2] RISC-V: make use of variadic sbi_ecall Radim Krčmář
2026-10-06 9:55 ` Paul Walmsley
2026-10-07 9:28 ` Radim Krcmar
2026-10-08 2:46 ` Paul Walmsley [this message]
2026-10-08 18:35 ` Anirudh Srinivasan
2025-06-19 19:03 ` [PATCH v2 3/2] RISC-V: sbi: remove sbi_ecall tracepoints Radim Krčmář
2025-06-23 22:54 ` Palmer Dabbelt
2025-06-24 13:09 ` Radim Krčmář
2025-06-25 7:51 ` Radim Krčmář
2025-06-25 8:34 ` David Laight
2025-06-26 8:10 ` Radim Krčmář
2025-06-23 22:53 ` [PATCH v2 0/2] RISC-V: turn sbi_ecall into a variadic macro Palmer Dabbelt
2025-06-24 8:09 ` David Laight
2025-06-24 12:40 ` Radim Krčmář
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=d94ecb9c-def7-a9cb-456b-60b18489d0f3@kernel.org \
--to=pjw@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=atishp@rivosinc.com \
--cc=cleger@rivosinc.com \
--cc=david.laight.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv-bounces@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rkrcmar@qti.qualcomm.com \
--cc=thomas.weissschuh@linutronix.de \
/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®