From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] arm64: mm: increase VA range of identity map
Date: Thu, 26 Feb 2015 11:27:18 +0000 [thread overview]
Message-ID: <20150226112717.GA17992@localhost> (raw)
In-Reply-To: <1424942215-5505-1-git-send-email-ard.biesheuvel@linaro.org>
On Thu, Feb 26, 2015 at 09:16:55AM +0000, Ard Biesheuvel wrote:
> The page size and the number of translation levels, and hence the supported
> virtual address range, are build-time configurables on arm64 whose optimal
> values are use case dependent. However, in the current implementation, if
> the system's RAM is located at a very high offset, the virtual address range
> needs to reflect that merely because the identity mapping, which is only used
> to enable or disable the MMU, requires the extended virtual range to map the
> physical memory at an equal virtual offset.
>
> This patch relaxes that requirement, by increasing the number of translation
> levels for the identity mapping only, and only when actually needed, i.e.,
> when system RAM's offset is found to be out of reach at runtime.
>
> Tested-by: Laura Abbott <lauraa@codeaurora.org>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
The patch looks fine to me, though most likely for 4.1; in the meantime:
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Do you plan to look at the KVM aspect as well or we leave it with the
KVM maintainers?
--
Catalin
next prev parent reply other threads:[~2015-02-26 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 9:16 [PATCH v3] arm64: mm: increase VA range of identity map Ard Biesheuvel
2015-02-26 11:27 ` Catalin Marinas [this message]
2015-02-26 11:35 ` Ard Biesheuvel
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=20150226112717.GA17992@localhost \
--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 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.