From: wangkefeng.wang@huawei•com (Kefeng Wang)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC PATCH] arm64: Expose physical/virtual address bits through cpuinfo
Date: Mon, 21 Mar 2016 19:58:42 +0800 [thread overview]
Message-ID: <56EFE1F2.8080409@huawei.com> (raw)
In-Reply-To: <20160318121325.GB4645@e104818-lin.cambridge.arm.com>
On 2016/3/18 20:13, Catalin Marinas wrote:
> On Thu, Mar 17, 2016 at 06:08:03PM +0800, Kefeng Wang wrote:
>> AArch64 support six types Physical Address range, permitted values
>> in ID_AA64MMFR0_EL1 are:
>> 0000 32 bits, 4GB.
>> 0001 36 bits, 64GB.
>> 0010 40 bits, 1TB.
>> 0011 42 bits, 4TB.
>> 0100 44 bits, 16TB.
>> 0101 48 bits, 256TB.
>> All other values are reserved.
>>
>> Meanwhile, AArch64 allows 36-bit, 39-bit, 42-bit, 47-bit and 48-bit
>> virtual addresses.
>>
>> Exposing the physical and virtual address bits to userspace through
>> procfs like x86, then it is easy to check them from cpuinfo.
>
> So, what does user space need such information for?
For now, no user app use this, it just shows the physical/virtual address size
that is supported by cpu.
AArch64 supports several different types of physical/virtual address bits(up to 52bit
in ARMv8.2 especially), I think it's better to expose it, and cpuinfo is proper space.
prev parent reply other threads:[~2016-03-21 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 10:08 [RFC PATCH] arm64: Expose physical/virtual address bits through cpuinfo Kefeng Wang
2016-03-17 11:31 ` Suzuki K. Poulose
2016-03-18 5:47 ` Kefeng Wang
2016-03-18 10:12 ` Suzuki K. Poulose
2016-03-18 12:13 ` Catalin Marinas
2016-03-21 11:58 ` Kefeng Wang [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=56EFE1F2.8080409@huawei.com \
--to=wangkefeng.wang@huawei$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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