From: Sven Peter <sven@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Sudeep Holla <sudeep.holla@kernel.org>,
Janne Grunau <j@jannau.net>, Neal Gompa <neal@gompa.dev>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
asahi@lists.linux.dev
Subject: Re: [PATCH RFC 0/6] PSCI-via-EFI to support firmware and kernel sharing EL2 for Apple Silicon
Date: Thu, 3 Sep 2026 18:26:18 +0200 [thread overview]
Message-ID: <acdf2acc-a1a7-4a02-8924-4605e0d929b0@kernel.org> (raw)
In-Reply-To: <9c53cfd7-e193-4441-83ca-7710060225b7@app.fastmail.com>
Hi Ard,
On 03.09.26 13:34, Ard Biesheuvel wrote:
> Hi Sven,
>
> On Wed, 8 Jul 2026, at 09:15, Sven Peter wrote:
>> Hi,
>>
>> Usually, idle and sleep state are implemented in firmware running in
>> e.g. EL3 with the kernel trapping into that from EL2. Unfortunately,
>> there's no EL3 on Apple Silicon machines and we'd rather not run the
>> kernel in EL1 since this would result in losing KVM support.
>>
>> While the shallower states could be implemented inside a custom cpuidle
>> driver (like we do downstream, see [1]) the deeper states result in a
>> complete loss of state and require bootstraping the cores again which is
>> quite involved. So instead we need some way to call back into our
>> open-source firmware to be able to handle that. This is even more
>> important for M4+ which don't even support the architectural wfi anymore
>> and always lose state when that instruction is executed.
>>
>> Luckily, EFI runtime services provide much of scaffolding we need,
>> namely a way to keep some code and data mapped and the ability to jump
>> into there from inside the kernel.
>>
>> This series adds a custom EFI table that points to a PSCI entry point
>> (plus some other stuff that has to be available before EFI runtime
>> services are set up) and adds support for this new conduit to the psci
>> code. We can't directly use the normal EFI runtime path because that one
>> takes a sleeping lock and we need to be able to call into PSCI from
>> atomic context during e.g. cpu bringup or during idle.
>> It also adds support for specifying the specific MAIR attributes for EFI
>> runtime mappings as defined in the latest UEFI spec since Apple Silicon
>> is rather allergic to using Device-nGnRnE vs. Device-nGnRE for its MMIO.
>>
>> This all results in a surprisingly small diffstat. I believe this
>> approach was originally suggested in some IRC discussion years ago,
>> possibly by Ard, but I can't find the old logs anymore.
>> Happy to add a Suggested-by tag though if anyone remembers.
>>
>> The firmware implementation I used for testing can be found at [2] and
>> the full kernel tree with this series applied at [3].
>>
>> Best,
>>
>> Sven
>>
>> [1]
>> https://github.com/AsahiLinux/linux/blob/asahi/drivers/cpuidle/cpuidle-apple.c
>> [2] https://github.com/AsahiLinux/m1n1/tree/psci-via-efi
>> [3]
>> https://git.kernel.org/pub/scm/linux/kernel/git/sven/linux.git/log/?h=efi-psci
>>
>> Signed-off-by: Sven Peter <sven@kernel.org>
>> ---
>> Sven Peter (6):
>> dt-bindings: arm: psci: Add EFI conduit
>> arm64/efi: Add and parse custom PSCI EFI configuration table
>> efi: Add EFI_MEMORY_ISA_{MASK,VALID}
>> arm64/efi: Honor EFI_MEMORY_ISA_MASK for Device-nGnRnE vs -nGnRE
>> firmware/psci: Add EFI runtime conduit
>> arm64: dts: apple: t8103: Add PSCI and CPU idle states
>>
>
> I've picked up patches #3 and #4, which are useful in their own right.
thanks, I think i had a fixup for one of those in my local v2. I'll
check and send it as a separate patch if it was important.
>
> I'm not sure if the arm64 maintainers will want to consider this, but
> I think it's a reasonable compromise, as it puts the abstraction in
> the right place.
>
> I take it this will be contributed to u-boot if it gets accepted here?
Yeah, that was my plan: First agree on something that can be accepted
into the kernel and then work on the rest of the boot chain. The current
code in m1n1 that sets up bare bones EFI tables is just a hack to proof
this all actually works.
Sven
prev parent reply other threads:[~2026-09-03 16:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 7:15 [PATCH RFC 0/6] PSCI-via-EFI to support firmware and kernel sharing EL2 for Apple Silicon Sven Peter
2026-07-08 7:15 ` [PATCH RFC 1/6] dt-bindings: arm: psci: Add EFI conduit Sven Peter
2026-07-08 7:15 ` [PATCH RFC 2/6] arm64/efi: Add and parse custom PSCI EFI configuration table Sven Peter
2026-07-08 7:39 ` sashiko-bot
2026-07-08 7:15 ` [PATCH RFC 3/6] efi: Add EFI_MEMORY_ISA_{MASK,VALID} Sven Peter
2026-07-08 7:25 ` sashiko-bot
2026-07-08 7:15 ` [PATCH RFC 4/6] arm64/efi: Honor EFI_MEMORY_ISA_MASK for Device-nGnRnE vs -nGnRE Sven Peter
2026-07-08 7:33 ` sashiko-bot
2026-07-08 7:15 ` [PATCH RFC 5/6] firmware/psci: Add EFI runtime conduit Sven Peter
2026-07-08 7:46 ` sashiko-bot
2026-07-08 7:15 ` [PATCH RFC 6/6] arm64: dts: apple: t8103: Add PSCI and CPU idle states Sven Peter
2026-07-08 7:48 ` sashiko-bot
2026-09-03 11:34 ` [PATCH RFC 0/6] PSCI-via-EFI to support firmware and kernel sharing EL2 for Apple Silicon Ard Biesheuvel
2026-09-03 11:42 ` Mark Rutland
2026-09-03 12:15 ` Will Deacon
2026-09-03 13:25 ` Ard Biesheuvel
2026-09-03 16:26 ` Sven Peter [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=acdf2acc-a1a7-4a02-8924-4605e0d929b0@kernel.org \
--to=sven@kernel.org \
--cc=ardb@kernel.org \
--cc=asahi@lists.linux.dev \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=j@jannau.net \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=neal@gompa.dev \
--cc=robh@kernel.org \
--cc=sudeep.holla@kernel.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).