From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: ian.jackson@eu.citrix.com, stefano.stabellini@eu.citrix.com,
tim@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH v3 03/14] xen: arm: allocate dom0 memory separately from preparing the dtb
Date: Mon, 11 Nov 2013 12:25:31 +0000 [thread overview]
Message-ID: <5280CCBB.4090008@linaro.org> (raw)
In-Reply-To: <1384171931.8909.47.camel@kazak.uk.xensource.com>
On 11/11/2013 12:12 PM, Ian Campbell wrote:
> On Mon, 2013-11-11 at 12:08 +0000, Julien Grall wrote:
>> On 11/08/2013 09:36 AM, Ian Campbell wrote:
>>> On Thu, 2013-11-07 at 23:18 -0800, Julien Grall wrote:
>>> I think
>>> / {
>>> "memory" {
>>> #address-cells = 2;
>>> #size-cells = 2;
>>> device_type = "memory";
>>> reg = <...>;
>>> }
>>> }
>>>
>>> Won't work because the #foo-cells only applies to children.
>>>
>>> I could do
>>> / {
>>> "memory" {
>>> #address-cells = 2;
>>> #size-cells = 2;
>>> "memory@foo" {
>>> device_type = "memory"
>>> reg = <...>;
>>> }
>>> }
>>> }
>>>
>>> which puts the size under my control.
>>
>> I have noticed that we have the same issue on the other nodes (gic,
>> timer,...).
>
> The timer node at least doesn't have any regions, does it? But for gic
> yes this is trouble.
>
>> Perhaps we can create a node "xen" which contains all the
>> devices?
>
> Would it be bogus to put them in the existing hypervisor node?
I don't think so.
--
Julien Grall
next prev parent reply other threads:[~2013-11-11 12:25 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 16:44 [PATCH v3 00/14] xen: arm: 64-bit guest support and domU FDT autogeneration Ian Campbell
2013-11-07 16:44 ` [PATCH v3 01/14] xen: arm: Report aarch64 capability Ian Campbell
2013-11-07 16:44 ` [PATCH v3 02/14] xen: arm: Add comment regard arm64 zImage v0 vs v1 Ian Campbell
2013-11-07 16:44 ` [PATCH v3 03/14] xen: arm: allocate dom0 memory separately from preparing the dtb Ian Campbell
2013-11-08 7:18 ` Julien Grall
2013-11-08 9:36 ` Ian Campbell
2013-11-11 12:08 ` Julien Grall
2013-11-11 12:12 ` Ian Campbell
2013-11-11 12:25 ` Julien Grall [this message]
2013-11-11 13:17 ` Stefano Stabellini
2013-11-07 16:44 ` [PATCH v3 04/14] xen: arm: add enable-method to cpu nodes for arm64 guests Ian Campbell
2013-11-07 16:44 ` [PATCH v3 05/14] xen: arm: implement XEN_DOMCTL_set_address_size Ian Campbell
2013-11-11 12:13 ` Julien Grall
2013-11-07 16:44 ` [PATCH v3 06/14] xen: arm: implement arch_set_info_guest for 64-bit vcpus Ian Campbell
2013-11-08 7:20 ` Julien Grall
2013-11-07 16:44 ` [PATCH v3 07/14] tools: check for libfdt when building for ARM Ian Campbell
2013-11-07 17:04 ` Ian Jackson
2013-11-07 16:44 ` [PATCH v3 08/14] xen: arm: define guest virtual platform in API headers Ian Campbell
2013-11-08 7:29 ` Julien Grall
2013-11-08 9:48 ` Ian Campbell
2013-11-11 14:25 ` Julien Grall
2013-11-11 15:12 ` Ian Campbell
2013-11-07 16:44 ` [PATCH v3 09/14] libxc: arm: rename various bits of zimage load with 32 suffix Ian Campbell
2013-11-07 16:44 ` [PATCH v3 10/14] libxc: allow caller to specify guest rambase rather than hardcoding Ian Campbell
2013-11-07 17:06 ` Ian Jackson
2013-11-07 17:09 ` Ian Campbell
2013-11-07 17:30 ` Ian Jackson
2013-11-07 16:44 ` [PATCH v3 11/14] libxc: allow passing a device tree blob to the guest Ian Campbell
2013-11-07 17:09 ` Ian Jackson
2013-11-07 17:10 ` Ian Campbell
2013-11-07 17:31 ` Ian Jackson
2013-11-07 17:42 ` Ian Campbell
2013-11-12 10:46 ` Ian Campbell
2013-11-07 16:44 ` [PATCH v3 12/14] libxc: support for arm64 Image format Ian Campbell
2013-11-11 14:28 ` Julien Grall
2013-11-07 16:44 ` [PATCH v3 13/14] libxc: arm64 vcpu initialisation Ian Campbell
2013-11-07 17:09 ` Ian Jackson
2013-11-11 15:03 ` Julien Grall
2013-11-07 16:44 ` [PATCH v3 14/14] libxl: build a device tree for ARM guests Ian Campbell
2013-11-07 17:30 ` Ian Jackson
2013-11-07 17:41 ` Ian Campbell
2013-11-07 17:47 ` Ian Jackson
2013-11-08 9:30 ` Ian Campbell
2013-11-08 15:14 ` Ian Jackson
2013-11-11 12:14 ` Ian Campbell
2013-11-12 10:51 ` 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=5280CCBB.4090008@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=ian.jackson@eu.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).