From: Paul Walmsley <pjw@kernel.org>
To: Atish Patra <atish.patra@linux.dev>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
linux-efi@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, Atish Patra <atishp@meta.com>
Subject: Re: [PATCH 0/2] riscv: Use EFI runtime services for poweroff and restart
Date: Thu, 25 Jun 2026 14:14:54 -0600 (MDT) [thread overview]
Message-ID: <0167594c-0c54-cbb0-a981-26df2a5bfb3c@kernel.org> (raw)
In-Reply-To: <20260615-efi_reset_shutdown-v1-0-9414edcbbab0@meta.com>
On Mon, 15 Jun 2026, Atish Patra wrote:
> Today RISC-V always uses the SBI SRST extension for both poweroff and restart,
> even when UEFI runtime services are available. This series makes RISC-V prefer
> EFI runtime services for both paths when available. The reset via EFI is
> required for EFI capsule updates and also documented as a preferred method
> in BRS 1.0 spec (e.g. URT_030)[1]
>
> Behavior on SBI-only (non-EFI) systems is unchanged.
>
> Tested under QEMU 'virt' with EDK2/UEFI firmware exposing runtime
> ResetSystem().
>
> [1] https://docs.riscv.org/reference/brs/uefi.html#uefi
>
> Signed-off-by: Atish Patra <atishp@meta.com>
Thanks, queued for v7.3.
- Paul
prev parent reply other threads:[~2026-06-25 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 23:28 Atish Patra
2026-06-15 23:28 ` [PATCH 1/2] riscv: efi: Power off via EFI runtime services when available Atish Patra
2026-06-16 4:29 ` Sunil V L
2026-06-15 23:28 ` [PATCH 2/2] riscv: Restart " Atish Patra
2026-06-16 4:29 ` Sunil V L
2026-06-25 20:14 ` Paul Walmsley [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=0167594c-0c54-cbb0-a981-26df2a5bfb3c@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=atish.patra@linux.dev \
--cc=atishp@meta.com \
--cc=ilias.apalodimas@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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
Powered by JetHome