From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel <xen-devel@lists.xen.org>
Cc: Stefano Stabellini <stefano.stabellini@citrix.com>,
julien Grall <julien.grall@linaro.org>, Tim Deegan <tim@xen.org>,
'Pranavkumar Sawargaonkar <psawargaonkar@apm.com>,
Anup Patel <anup.patel@linaro.org>
Subject: Re: [PATCH v2 0/6] xen: arm: fixups for systems with RAM above 4GB
Date: Mon, 21 Oct 2013 10:35:28 +0100 [thread overview]
Message-ID: <1382348128.1657.9.camel@hastur.hellion.org.uk> (raw)
In-Reply-To: <1381416204.17758.36.camel@kazak.uk.xensource.com>
Keir acked the generic bit, but ping on the ARM specific patches?
Thanks,
Ian.
On Thu, 2013-10-10 at 15:43 +0100, Ian Campbell wrote:
> This is primarily an attempt to get arm64 Xen working on systems which
> do not have any RAM at all below 4GB but there are small fixes for
> systems with highmem generally.
>
> I've been testing this with a hack DTB which uses only the AEM
> fastmodel's 36-bit alias of DRAM and a hacked up boot-wrapper to load at
> the appropriate addresses etc.
>
> The first patch "xen: correct xenheap_bits after "xen: support RAM at
> addresses 0 and 4096" has been previously posted as a standalone patch.
>
> Since v1 I have fixed the issue with not being able to actually build a
> guest (needed to set HCR_EL2.RW correctly). This version now loads the
> dom0 kernel successfully.
>
> I've also pushed to xenbits:
>
> The following changes since commit 1e143e2ae8be3ba86c2e931a1ee8d91efca08f89:
>
> libxl: correctly handle libxl_get_cpu_topology failure in libxl_{cpu, node}map_to_{node, cpu}map (2013-10-03 14:45:54 +0100)
>
> are available in the git repository at:
>
> git://xenbits.xen.org/people/ianc/xen.git no-low-ram-v2
>
> for you to fetch changes up to 619d081e1df07d3abad2c73eca494b27ac1b266b:
>
> xen: arm: Ensure HCR_EL2.RW is set correctly when building dom0 (2013-10-10 15:28:03 +0100)
>
> ----------------------------------------------------------------
> Ian Campbell (6):
> xen: correct xenheap_bits after "xen: support RAM at addresses 0 and 4096"
> xen: arm: Enable 40 bit addressing in VTCR for arm64
> xen: arm: map entire memory banks on arm64
> xen: arm: make sure pagetable mask macros have appropriate size
> xen: arm: correctly round down MFN to 1GB boundary make sure pagetable mask macros as physaddr size
> xen: arm: Ensure HCR_EL2.RW is set correctly when building dom0
>
> xen/arch/arm/domain_build.c | 10 +++++++---
> xen/arch/arm/mm.c | 13 ++++++++++---
> xen/arch/arm/setup.c | 4 ++--
> xen/common/page_alloc.c | 2 +-
> xen/include/asm-arm/page.h | 20 ++++++++++----------
> 5 files changed, 30 insertions(+), 19 deletions(-)
>
>
> Ian.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-10-21 9:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 14:43 [PATCH v2 0/6] xen: arm: fixups for systems with RAM above 4GB Ian Campbell
2013-10-10 14:43 ` [PATCH 1/6] xen: correct xenheap_bits after "xen: support RAM at addresses 0 and 4096" Ian Campbell
2013-10-10 15:14 ` Keir Fraser
2013-10-10 14:43 ` [PATCH 2/6] xen: arm: Enable 40 bit addressing in VTCR for arm64 Ian Campbell
2013-10-21 15:56 ` Julien Grall
2013-10-10 14:43 ` [PATCH 3/6] xen: arm: map entire memory banks on arm64 Ian Campbell
2013-10-23 13:54 ` Julien Grall
2013-10-10 14:43 ` [PATCH 4/6] xen: arm: make sure pagetable mask macros have appropriate size Ian Campbell
2013-10-21 15:53 ` Julien Grall
2013-10-10 14:43 ` [PATCH 5/6] xen: arm: correctly round down MFN to 1GB boundary make sure pagetable mask macros as physaddr size Ian Campbell
2013-10-23 13:52 ` Julien Grall
2013-10-10 14:43 ` [PATCH 6/6] xen: arm: Ensure HCR_EL2.RW is set correctly when building dom0 Ian Campbell
2013-10-23 10:39 ` Julien Grall
2013-10-23 10:41 ` Julien Grall
2013-10-21 9:35 ` Ian Campbell [this message]
2013-10-23 13:55 ` [PATCH v2 0/6] xen: arm: fixups for systems with RAM above 4GB Julien Grall
2013-10-24 14:07 ` Ian Campbell
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=1382348128.1657.9.camel@hastur.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=anup.patel@linaro.org \
--cc=julien.grall@linaro.org \
--cc=psawargaonkar@apm.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--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 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).