From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Junxiao Chang" <junxiao.chang@intel.com>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>
Subject: Re: [PATCH] efi: add dynamic control interface for EFI runtime services
Date: Thu, 03 Sep 2026 12:08:31 +0200 [thread overview]
Message-ID: <be731d49-398b-4b5b-9de5-b94d53177f94@app.fastmail.com> (raw)
In-Reply-To: <20260815095057.2461943-1-junxiao.chang@intel.com>
On Sat, 15 Aug 2026, at 11:50, Junxiao Chang wrote:
> Add an interface for PREEMPT_RT kernels to dynamically enable or
> disable EFI runtime services.
>
> EFI runtime services are typically disabled on RT systems using
> kernel parameters such as "noefi" or "efi=disable" to avoid
> long latency caused by firmware calls. However, this permanently
> disables EFI runtime services, preventing operations such as UEFI
> firmware updates.
>
> With this change, EFI runtime services can be disabled while
> real-time workloads are running and re-enabled afterwards,
> providing low-latency operation without permanently sacrificing
> firmware functionality.
>
> Signed-off-by: Junxiao Chang <junxiao.chang@intel.com>
> ---
> drivers/firmware/efi/efi.c | 31 +++++++++++++++++++++++++
> drivers/firmware/efi/runtime-wrappers.c | 28 ++++++++++++++++++++++
> include/linux/efi.h | 1 +
> 3 files changed, 60 insertions(+)
>
I've queued this up now - thanks.
prev parent reply other threads:[~2026-09-03 10:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 0:33 [PATCH] mefi: add dynamic control interface for EFI runtime services Junxiao Chang
2026-07-23 6:37 ` Ard Biesheuvel
2026-07-30 6:14 ` Chang, Junxiao
2026-08-12 14:41 ` Sebastian Andrzej Siewior
2026-08-13 8:12 ` Chang, Junxiao
2026-07-31 6:24 ` [PATCH] efi: " Junxiao Chang
2026-08-01 13:45 ` Ard Biesheuvel
2026-08-06 9:49 ` Junxiao Chang
2026-08-15 9:50 ` Junxiao Chang
2026-09-03 10:08 ` Ard Biesheuvel [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=be731d49-398b-4b5b-9de5-b94d53177f94@app.fastmail.com \
--to=ardb@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=ilias.apalodimas@linaro.org \
--cc=junxiao.chang@intel.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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