From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/2] arm64: Add support for 48-bit Physical Addresses
Date: Thu, 5 Dec 2013 17:30:37 +0000 [thread overview]
Message-ID: <20131205173036.GE17165@arm.com> (raw)
In-Reply-To: <CAC8NTUUHiaB3m+zmoPPKXTzWq82veNhT4gCERSQiLvKhfMvRyQ@mail.gmail.com>
On Thu, Dec 05, 2013 at 02:35:52PM +0000, Radha Mohan wrote:
> Before going for a next version of patch to fix breaking SMMU and KVM,
> I would like to know about the best possible implementation.
> Should I go for a compile time option? I am not in favor of this. What
> are options if in future there's 16KB page support in the kernel.
As I said in the other email, separate the shifts definitions (primarily
page size dependent) from the type definitions (dependent on the number
of levels).
Just to understand your requirements better. Does your platform have
more than 256GB of RAM? With the current configuration, the VA space is
39-bit with 4K (which would allow 512GB minus some vmalloc and modules
space) and 42-bit with 64K pages (2TB minus vmalloc/modules).
--
Catalin
next prev parent reply other threads:[~2013-12-05 17:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 7:34 [RFC PATCH 0/2] arm64: Add support for 48-bit Physical Addresses mohun106 at gmail.com
2013-11-27 7:34 ` [RFC PATCH 1/2] arm64: Add 48-bit PA support for 4KB page size mohun106 at gmail.com
2013-11-27 11:14 ` Mark Rutland
2013-11-27 16:00 ` Radha Mohan
2013-11-27 7:34 ` [RFC PATCH 2/2] arm64: Add 48-bit PA support for 64KB " mohun106 at gmail.com
2013-11-27 11:30 ` Mark Rutland
2013-11-27 11:04 ` [RFC PATCH 0/2] arm64: Add support for 48-bit Physical Addresses Marc Zyngier
2013-11-27 15:33 ` Radha Mohan
2013-11-27 15:50 ` Will Deacon
2013-11-27 17:59 ` Marc Zyngier
2013-11-28 2:14 ` Radha Mohan
2013-12-05 14:35 ` Radha Mohan
2013-12-05 15:10 ` Marc Zyngier
2013-12-05 17:30 ` Catalin Marinas [this message]
2013-12-10 16:53 ` Radha Mohan
2013-12-10 17:02 ` Catalin Marinas
2013-12-11 9:18 ` Radha Mohan
2013-12-05 16:53 ` Catalin Marinas
2013-11-28 9:29 ` Steve Capper
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=20131205173036.GE17165@arm.com \
--to=catalin.marinas@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 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).