From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: linux-kernel@vger.kernel.org, Peter Jones <pjones@redhat.com>,
Alexander Larsson <alexl@redhat.com>, Al Stone <ahs3@redhat.com>,
linux-efi@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
Andrew Halaney <ahalaney@redhat.com>,
linux-rt-users@vger.kernel.org, Brian Masney <bmasney@redhat.com>,
Robbie Harwood <rharwood@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] efi: Allow to enable EFI runtime services with PREEMPT_RT
Date: Thu, 31 Mar 2022 16:13:38 +0200 [thread overview]
Message-ID: <YkW3EmURxE1+kOu5@linutronix.de> (raw)
In-Reply-To: <20220331141038.171204-1-javierm@redhat.com>
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
next prev parent reply other threads:[~2022-03-31 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 14:10 Javier Martinez Canillas
2022-03-31 14:13 ` Sebastian Andrzej Siewior [this message]
2022-03-31 14:25 ` Javier Martinez Canillas
2022-03-31 14:40 ` Sebastian Andrzej Siewior
2022-03-31 14:50 ` Javier Martinez Canillas
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=YkW3EmURxE1+kOu5@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=ahalaney@redhat.com \
--cc=ahs3@redhat.com \
--cc=alexl@redhat.com \
--cc=ardb@kernel.org \
--cc=bmasney@redhat.com \
--cc=javierm@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pjones@redhat.com \
--cc=rharwood@redhat.com \
--cc=tglx@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®