From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rt-devel@lists.linux.dev,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
John Ogness <john.ogness@linutronix.de>,
Lai Jiangshan <jiangshanlai@gmail.com>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH 0/2] efi: Expose the runtime-services workqueue via sysfs
Date: Thu, 12 Feb 2026 16:18:35 +0100 [thread overview]
Message-ID: <20260212151835.8On7hOkI@linutronix.de> (raw)
In-Reply-To: <4c6a5533-6fcd-4237-bb35-0ca74029c7db@app.fastmail.com>
On 2026-02-09 18:10:52 [+0100], Ard Biesheuvel wrote:
> Hello Sebastian,
>
> On Thu, 5 Feb 2026, at 12:55, Sebastian Andrzej Siewior wrote:
> > EFI runtime services are disabled on PREEMPT_RT by default which can be
> > overwritten on the boot command line. For native EFI, an invocation
> > requires to disable preemption while a call is made into EFI.
>
> This is no longer true on arm64 since
>
> commit a5baf582f4c026c25a206ac121bceade926aec74
> Author: Ard Biesheuvel <ardb@kernel.org>
> Date: Wed Oct 15 22:56:42 2025 +0200
>
> arm64/efi: Call EFI runtime services without disabling preemption
>
> except for some corner cases (reboot, pstore crash dump).
Hmm. While this sounds familiar (and I think you told me that FPU usage
no longer disables preemption here, too) there is x86 for instance. Here
arch_efi_call_virt_setup() disables preemption twice (efi_fpu_begin() +
(firmware_restrict_branch_speculation_start()) followed by
efi_call_virt_save_flags() where interrupts are off.
Also I don't know if the EFI implementation itself is allowed to disable
interrupts.
> > There are two EFI invocations which are not covered by this
> > - mixed EFI
> > Used on x86 with 64bit kernel but 32bit EFI. Would it work to use here
> > the same workqueue mechanism?
> >
>
> That stuff is beyond obsolete, so I don't think it is relevant for RT.
agreed.
> Acked-by: Ard Biesheuvel <ardb@kernel.org>
Oh. Thank you.
Sebastian
prev parent reply other threads:[~2026-02-12 15:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 11:55 [PATCH 0/2] efi: Expose the runtime-services workqueue via sysfs Sebastian Andrzej Siewior
2026-02-05 11:55 ` [PATCH 1/2] workqueue: Allow to expose ordered workqueues " Sebastian Andrzej Siewior
2026-02-05 13:39 ` Sebastian Andrzej Siewior
2026-02-05 21:59 ` Tejun Heo
2026-02-05 11:55 ` [PATCH 2/2] efi: Allow to expose the workqueue " Sebastian Andrzej Siewior
2026-02-09 15:17 ` [PATCH 0/2] efi: Expose the runtime-services " Luis Claudio R. Goncalves
2026-02-09 15:55 ` Sebastian Andrzej Siewior
2026-02-12 7:09 ` Ilias Apalodimas
2026-02-12 16:20 ` Sebastian Andrzej Siewior
2026-02-13 6:28 ` Ilias Apalodimas
2026-02-09 17:10 ` Ard Biesheuvel
2026-02-12 15:18 ` Sebastian Andrzej Siewior [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=20260212151835.8On7hOkI@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=ardb@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=john.ogness@linutronix.de \
--cc=lgoncalv@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=tj@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