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:40:15 +0200 [thread overview]
Message-ID: <YkW9T2xRSI9e4BFv@linutronix.de> (raw)
In-Reply-To: <ce8d975e-d9dd-f9b8-793d-234258021169@redhat.com>
On 2022-03-31 16:25:40 [+0200], Javier Martinez Canillas wrote:
> Hello Sebastian,
Hi Javier,
> Yes, it is but the motivation is to be able to have EFI runtime services
> by default without the need for any kernel command line parameter.
This part wasn't clear. It is not mentioned by the description but now
that I look at Kconfig, it is there.
> In the same vein, I could ask if efi=noruntime wasn't enough instead of
> commit ("efi: Disable runtime services on RT").
No, it is not because it should not lead to any surprise latencies by
default.
Sebastian
next prev parent reply other threads:[~2022-03-31 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 14:10 [PATCH] efi: Allow to enable EFI runtime services with PREEMPT_RT Javier Martinez Canillas
2022-03-31 14:13 ` Sebastian Andrzej Siewior
2022-03-31 14:25 ` Javier Martinez Canillas
2022-03-31 14:40 ` Sebastian Andrzej Siewior [this message]
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=YkW9T2xRSI9e4BFv@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