From: "Alex Bennée" <alex.bennee@linaro.org>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: qemu-arm@nongnu.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: How to get the supported page sizes of aarch64? (and possible other architectures)
Date: Fri, 07 Jan 2022 11:46:58 +0000 [thread overview]
Message-ID: <87tuefhhyt.fsf@linaro.org> (raw)
In-Reply-To: <9405dfb2-01ea-d11c-5e8a-f0db5db73204@gmx.com>
Qu Wenruo <quwenruo.btrfs@gmx.com> writes:
> Hi,
>
> Recently I'm trying to boot a kernel with 16K page size, but edk2
> firmware failed to load the kernel on my CM4, with unsupported message:
>
> Failed to execute Archlinux ARM (\Image-custom): Unsupported
>
> While 4K and 64K page sized kernels are fine to boot.
>
> A quick search shows that Cortex A processors support 4K and 64K page
> size, and 16K page size is not a mandatory requirement.
>
> On the other hand, other aarch64 processors, like Apple M1 only supports
> 4K and 16K page size, no 64K page size support.
>
>
> Although ARM documents show ID_AA64MMFR0_EL1 would report such info, is
> there any user space tool or kernel messages to show an
> end-user-friendly output about what page sizes are support?
Not that I'm aware of but a chunk of the ID registers are exposed to
user space to read (although some bits are masked). I think the kernel
hides the translation granules support and I think only exposes the page
size the kernel has booted into.
I guess you could hack the kernel to dump the real ID register value in
dmesg or something like that?
>
> Thanks,
> Qu
--
Alex Bennée
prev parent reply other threads:[~2022-01-07 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 23:44 How to get the supported page sizes of aarch64? (and possible other architectures) Qu Wenruo
2022-01-07 11:46 ` Alex Bennée [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=87tuefhhyt.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-arm@nongnu.org \
--cc=quwenruo.btrfs@gmx.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.