From: Karl Mehltretter <kmehltretter@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
Russell King <linux@armlinux.org.uk>,
Kevin Cernekee <cernekee@gmail.com>,
Gregory Fong <gregory.0xf0@gmail.com>
Subject: Re: [PATCH v2] ARM: set !LPAE MAX_PHYSMEM_BITS to 32 and remove IO_36
Date: Sat, 25 Jul 2026 00:06:43 +0200 [thread overview]
Message-ID: <amPhVKnTgESQQp7w@gmail.com> (raw)
In-Reply-To: <0d6dbd8f-c5c5-49d2-b36e-3cdd404eb55b@app.fastmail.com>
On Fri, Jul 24, 2026 at 08:31:35PM +0100, Arnd Bergmann wrote:
>
> I'm not sure why you remove remap_area_supersections() but keep
> create_36bit_mapping(). I would just remove that as well.
Sorry, my earlier explanation was confusing. create_36bit_mapping() is
not totally unreachable after this patch. The ARM EFI path can reach it
through:
efi_create_mapping()
-> create_mapping_late()
-> create_36bit_mapping()
I verified this with a modified EDK2 build under QEMU that advertised an
aligned, write-back EFI runtime memory descriptor above 4 GiB. The
kernel successfully created the mapping and enabled EFI runtime
services.
Admittedly, this is a synthetic configuration. Stock ARM32 EDK2
restricts allocations to below 4 GiB, and I believe the AArch32 UEFI
specification requires RAM in the UEFI memory map to be identity-mapped
during boot services. The test setup is therefore probably not a
conforming real-world firmware configuration.
Maybe you want to keep create_36bit_mapping() because of that?
Alternatively, if this should be considered unsupported, I can remove
it in v3 as you suggested.
If create_36bit_mapping() remains, I will update the commit message to
clarify that the patch removes 36-bit I/O mappings, while retaining the
generic supersection mapping path for domain-0 memory mappings.
Thanks,
Karl
prev parent reply other threads:[~2026-07-24 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 17:47 [PATCH v2] ARM: set !LPAE MAX_PHYSMEM_BITS to 32 and remove IO_36 Karl Mehltretter
2026-07-24 18:31 ` Arnd Bergmann
2026-07-24 22:06 ` Karl Mehltretter [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=amPhVKnTgESQQp7w@gmail.com \
--to=kmehltretter@gmail.com \
--cc=arnd@arndb.de \
--cc=cernekee@gmail.com \
--cc=gregory.0xf0@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
/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