From: Suzuki.Poulose@arm.com (Suzuki K. Poulose)
To: linux-arm-kernel@lists.infradead.org
Subject: 16KB PAGE_SIZE not work on DB410C
Date: Sat, 26 Dec 2015 11:52:03 +0000 [thread overview]
Message-ID: <567E7F63.80707@arm.com> (raw)
In-Reply-To: <6DB39B31-8902-4A03-A66B-DC75E90A1C1C@linaro.org>
On 25/12/15 12:24, Pingbo Wen wrote:
> Hi Ard
Pingbo
>> Cortex-A5x does not support 16 KB page size
>
> Is there any documents I can reference? As I have get from ARM document, the Cortex-A53 support 16k page size, and Cortex-A57 don?t. The document can be found at:
>
> http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.den0024a/BABDJHAD.html
>
> Reference it here:
>
> The supported granule sizes are 4KB, 16KB, and 64KB, and it is implementation defined which of the three are supported. Code that creates page tables is able to read the system register ID_AA64MMFR0_EL1, to find out which are the supported sizes. The Cortex-A53 processor supports all three sizes, but this is not the case for early versions of some processors, such as the Cortex-A57, which did not support the 16K granule size. The size is configurable for each translation table within the Translation Control Register (TCR_EL1).
>
As it clearly says, it really depends on the implementation and by default A53 doesn't enable 16K support. If you have a debugger
could you check the $PC on the booting core and map it to the vmlinux symbol ? Please be aware that the address could be PA.
If the 16K is not supported the $PC will be in PA(__no_granule_support).
Cheers
Suzuki
next prev parent reply other threads:[~2015-12-26 11:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 4:00 16KB PAGE_SIZE not work on DB410C Pingbo Wen
2015-12-21 7:06 ` Ard Biesheuvel
2015-12-25 12:24 ` Pingbo Wen
2015-12-26 11:52 ` Suzuki K. Poulose [this message]
2015-12-31 9:05 ` Ard Biesheuvel
2016-01-11 12:18 ` Mark Rutland
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=567E7F63.80707@arm.com \
--to=suzuki.poulose@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 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.