[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <422e2a72-972f-41f4-a0b3-d69a6cb0c2e2@canonical.com>
Date: Mon, 14 Jul 2025 10:10:55 +0200
From: Heinrich Schuchardt <heinrich.schuchardt@...onical.com>
To: Ard Biesheuvel <ardb+git@...gle.com>
Cc: linux-arm-kernel@...ts.infradead.org, Ard Biesheuvel <ardb@...nel.org>,
Feng Tang <feng.tang@...ux.alibaba.com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Juergen Gross <jgross@...e.com>, Stefano Stabellini
<sstabellini@...nel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@...m.com>,
Sunil V L <sunilvl@...tanamicro.com>, Bibo Mao <maobibo@...ngson.cn>,
linux-rtc@...r.kernel.org, linux-efi@...r.kernel.org,
xen-devel@...ts.xenproject.org, x86@...nel.org,
linux-riscv@...ts.infradead.org, loongarch@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/3] Remove unused EFI runtime APIs
On 7/14/25 08:08, Ard Biesheuvel wrote:
> From: Ard Biesheuvel <ardb@...nel.org>
>
> Using EFI runtime services to program the RTC to wake up the system is
> supported in theory, but rarely works in practice. Fortunately, this
> functionality is rarely [if ever] used to begin with so we can just drop
> it. (Note that the EFI rtc driver is not used by x86, which programs the
> CMOS rtc directly)
The main problem I see with firmware offering access to the RTC via UEFI
services is that two different drivers, the firmware one and the Linux
one might be trying to access the same busses or registers which might
lead to unexpected results.
Recently there was a discussion in the RISC-V technical group for the
server platform specification where the same issue was discussed
concerning SetTime().
As a UEFI firmware should not care which operating system is booted, it
should be up to the OS to disable EFI access to the RTC if it has native
access.
Could we disable all the EFI services for the RTC in Linux dynamically
when an RTC driver is successfully probed?
Best regards
Heinrich
>
> The same applies to GetNextHighMonoCount(), which, if implemented,
> usually relies on SetVariable() under the hood *, which is often not
> supported at runtime by non-x86 platforms. But it has no known users
> either so let's drop support for it as well.
>
> This means we need to drop the slightly pointless tests for it too.
>
> * EDK2 based EFI implementations usually have a MTC variable carrying
> the monotonic counter variable, which is therefore not truly
> monotonic, given that SetVariable() will happily overwrite it.
>
> Cc: Heinrich Schuchardt <heinrich.schuchardt@...onical.com>
> Cc: Feng Tang <feng.tang@...ux.alibaba.com>
> Cc: Alexandre Belloni <alexandre.belloni@...tlin.com>
> Cc: Juergen Gross <jgross@...e.com>
> Cc: Stefano Stabellini <sstabellini@...nel.org>
> Cc: Oleksandr Tyshchenko <oleksandr_tyshchenko@...m.com>
> Cc: Sunil V L <sunilvl@...tanamicro.com>
> Cc: Bibo Mao <maobibo@...ngson.cn>
> Cc: linux-rtc@...r.kernel.org
> Cc: linux-efi@...r.kernel.org
> Cc: xen-devel@...ts.xenproject.org
> Cc: x86@...nel.org
> Cc: linux-riscv@...ts.infradead.org
> Cc: loongarch@...ts.linux.dev
>
> Ard Biesheuvel (3):
> efi-rtc: Remove wakeup functionality
> efi/test: Don't bother pseudo-testing unused EFI services
> efi: Remove support for pointless, unused EFI services
>
> arch/x86/platform/efi/efi_64.c | 22 ----
> drivers/firmware/efi/runtime-wrappers.c | 68 ------------
> drivers/firmware/efi/test/efi_test.c | 108 +-------------------
> drivers/rtc/rtc-efi.c | 76 +-------------
> drivers/xen/efi.c | 56 ----------
> include/linux/efi.h | 6 --
> 6 files changed, 4 insertions(+), 332 deletions(-)
>
Powered by blists - more mailing lists