[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YkW3EmURxE1+kOu5@linutronix.de>
Date: Thu, 31 Mar 2022 16:13:38 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Javier Martinez Canillas <javierm@...hat.com>
Cc: linux-kernel@...r.kernel.org, Peter Jones <pjones@...hat.com>,
Alexander Larsson <alexl@...hat.com>,
Al Stone <ahs3@...hat.com>, linux-efi@...r.kernel.org,
Ard Biesheuvel <ardb@...nel.org>,
Andrew Halaney <ahalaney@...hat.com>,
linux-rt-users@...r.kernel.org, Brian Masney <bmasney@...hat.com>,
Robbie Harwood <rharwood@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] efi: Allow to enable EFI runtime services with PREEMPT_RT
On 2022-03-31 16:10:38 [+0200], Javier Martinez Canillas wrote:
> Commit d9f283ae71af ("efi: Disable runtime services on RT") disabled EFI
> runtime services when the CONFIG_PREEMPT_RT option is enabled.
>
> The rationale for the change is that some EFI calls could take too much
> time, leading to large latencies which are an issue for RT kernels.
>
> But a side effect of that commit is that now is not possible anymore to
> enable the EFI runtime services by default when CONFIG_PREEMPT_RT is set
> to y, even for platforms that could guarantee bounded time for EFI calls.
>
> Instead, let's add a new EFI_DISABLE_RUNTIME boolean Kconfig option, that
> would be set to n by default but to y if CONFIG_PREEMPT_RT is enabled.
>
> That way, the current behaviour is preserved but gives users a mechanism
> to enable the EFI runtimes services in their kernels if that is required.
Is the command line switch
efi=runtime
not working?
Sebastian
Powered by blists - more mailing lists