From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: stefano.stabellini@eu.citrix.com, tim@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH v6 03/16] xen: arm: move dom0 gic and timer device tree nodes under /xen-core-devices/
Date: Tue, 19 Nov 2013 16:29:30 +0000 [thread overview]
Message-ID: <528B91EA.7040501@linaro.org> (raw)
In-Reply-To: <1384866024-13108-3-git-send-email-ian.campbell@citrix.com>
On 11/19/2013 01:00 PM, Ian Campbell wrote:
> Julien observed that we were relying on the provided host DTB supplying
> suitable #address-cells and #size-cells values to allow us to represent these
> addresses, which may not reliably be the case. Moving these under our own
> known (somewhat analogous to the use of /soc/ or /motherboard/ on some
> platforms) allows us to control these sizes.
>
> Since the new node is created out of thin air it does not have a corresponding
> struct dt_device_node and therefore we cannot use dt_n_addr_cells or
> dt_n_size_cells, we can use hardcoded constants instead. For the same reason
> we define and use set_xen_range instead of dt_set_range.
>
> The hypervisor, cpus and psci node all either defined #foo-cells for their
> children or do not contain reg properties and therefore can remain at the top
> level.
>
> The logging in make_gic_node was inconsistent. Fix it.
>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Acked-by: Julien Grall <julien.grall@linaro.org>
--
Julien Grall
next prev parent reply other threads:[~2013-11-19 16:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 12:59 [PATCH v6 00/16] xen: arm: 64-bit guest support and domU FDT autogeneration Ian Campbell
2013-11-19 13:00 ` [PATCH v6 01/16] xen: arm: Report aarch64 capability Ian Campbell
2013-11-19 13:00 ` [PATCH v6 02/16] xen: arm: Add comment regard arm64 zImage v0 vs v1 Ian Campbell
2013-11-19 13:00 ` [PATCH v6 03/16] xen: arm: move dom0 gic and timer device tree nodes under /xen-core-devices/ Ian Campbell
2013-11-19 14:05 ` Stefano Stabellini
2013-11-19 16:29 ` Julien Grall [this message]
2013-11-19 13:00 ` [PATCH v6 04/16] xen: arm: allocate dom0 memory separately from preparing the dtb Ian Campbell
2013-11-19 16:32 ` Julien Grall
2013-11-19 13:00 ` [PATCH v6 05/16] xen: arm: add enable-method to cpu nodes for arm64 guests Ian Campbell
2013-11-19 13:00 ` [PATCH v6 06/16] xen: arm: include header for for arch_do_{sys, dom}ctl prototype Ian Campbell
2013-11-19 13:00 ` [PATCH v6 07/16] xen: arm: implement XEN_DOMCTL_set_address_size Ian Campbell
2013-11-19 13:00 ` [PATCH v6 08/16] xen: arm: implement arch_set_info_guest for 64-bit vcpus Ian Campbell
2013-11-19 13:00 ` [PATCH v6 09/16] tools: check for libfdt when building for ARM Ian Campbell
2013-11-19 13:00 ` [PATCH v6 10/16] xen: arm: define guest virtual platform in API headers Ian Campbell
2013-11-19 17:58 ` Julien Grall
2013-11-19 13:00 ` [PATCH v6 11/16] libxc: arm: rename various bits of zimage load with 32 suffix Ian Campbell
2013-11-19 13:00 ` [PATCH v6 12/16] libxc: allow caller to specify guest rambase rather than hardcoding Ian Campbell
2013-11-19 13:00 ` [PATCH v6 13/16] libxc: arm: allow passing a device tree blob to the guest Ian Campbell
2013-11-19 16:34 ` Julien Grall
2013-11-19 13:00 ` [PATCH v6 14/16] libxc: support for arm64 Image format Ian Campbell
2013-11-19 13:00 ` [PATCH v6 15/16] libxc: arm64 vcpu initialisation Ian Campbell
2013-11-19 13:00 ` [PATCH v6 16/16] libxl: build a device tree for ARM guests Ian Campbell
2013-11-19 15:45 ` [PATCH v6 00/16] xen: arm: 64-bit guest support and domU FDT autogeneration George Dunlap
2013-11-19 16:42 ` 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=528B91EA.7040501@linaro.org \
--to=julien.grall@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.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).