From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel <xen-devel@lists.xen.org>
Cc: Julien Grall <julien.grall@linaro.org>, Tim Deegan <tim@xen.org>,
vijay.kilari@gmail.com,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: [PATCH v3 for-4.5 0/9] xen: arm: support for > 40-bit physical addressing
Date: Thu, 18 Sep 2014 01:09:20 +0100 [thread overview]
Message-ID: <1410998960.1920.2.camel@citrix.com> (raw)
ARM64 systems can support up to 48-bits of physical address, but
currently we configure both Stage-1 and Stage-2 for only 40-bits.
However there are systems with peripherals mapped higher up, in order to
support those we need to support 48-bits as output for stage-1 as well
as input and output for stage-2. Stage-2 support is needed in order to
map them 1:1 to dom0.
Unfortunately as the last commit message explains in a bit more detail
supporting larger input sizes on the p2m is a pain because it means we
can no longer statically decide to use a 3-level p2m with 2 concatenated
pages at the root and need to be able to support either that *or* a
4-level p2m with no root concatenation. There is simply no static choice
which supports both 40- and 48-bits of IPA.
So this series goes through the various functions which manipulate or
walk page tables and makes them able to support a dynamic starting level
and concatenation before switching arm64 to make the choice dependent on
the h/w capabilities.
This is somewhat loosely based on Vijay's original "Add 4-level page
table for stage 2 translation" series but due to the need to switch to
dynamic p2m levels not much of that remains.
I haven't actually been able to track down a system with >42-bit PASize.
Vijay, I'm hoping you can test this new version of the series on such a
system/model (thanks for your feed back on the previous iteration).
Since the last time I've addressed a bunch of review comments, see the
individual patches for details. Only the second patch is unacked. I'm
targeting this at 4.5.
Ian
next reply other threads:[~2014-09-18 0:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 0:09 Ian Campbell [this message]
2014-09-18 0:09 ` [PATCH v3 for-4.5 1/9] xen: arm: rename p2m->first_level to p2m->root Ian Campbell
2014-09-18 0:09 ` [PATCH v3 for-4.5 2/9] xen: arm: Implement variable levels in dump_pt_walk Ian Campbell
2014-09-22 14:33 ` Julien Grall
2014-09-18 0:09 ` [PATCH v3 for-4.5 3/9] xen: arm: handle concatenated root tables " Ian Campbell
2014-09-18 0:09 ` [PATCH v3 for-4.5 4/9] xen: arm: move setup_virt_paging to p2m.[ch] from mm.[ch] Ian Campbell
2014-09-18 0:09 ` [PATCH v3 for-4.5 5/9] xen: arm: Defer setting of VTCR_EL2 until after CPUs are up Ian Campbell
2014-09-18 0:09 ` [PATCH v3 for-4.5 6/9] xen: arm: handle variable p2m levels in p2m_lookup Ian Campbell
2014-09-18 0:09 ` [PATCH v3 for-4.5 7/9] xen: arm: handle variable p2m levels in apply_p2m_changes Ian Campbell
2014-09-18 0:09 ` [PATCH v3 for-4.5 8/9] xen: arm: support for up to 48-bit physical addressing on arm64 Ian Campbell
2014-09-18 0:09 ` [PATCH v3 for-4.5 9/9] xen: arm: support for up to 48-bit IPA " Ian Campbell
2014-09-19 14:46 ` [PATCH v3 for-4.5 0/9] xen: arm: support for > 40-bit physical addressing Vijay Kilari
2014-09-22 8:51 ` Ian Campbell
2014-09-22 13:25 ` Vijay Kilari
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=1410998960.1920.2.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=julien.grall@linaro.org \
--cc=tim@xen.org \
--cc=vijay.kilari@gmail.com \
--cc=xen-devel@lists.xen.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.