Re: [Xen-devel] [PATCH v3 03/14] xen: arm: allocate dom0 memory separately from preparing the dtb

[Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>]

On Mon, 11 Nov 2013, Julien Grall wrote:
> 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.

I don't like the idea: the hypervisor node is for hypervisor properties.
If you need another node to represent the soc, you can introduce a new
one. Maybe call it soc-xen or something like that, it could be

compatible = "simple-bus";

like many soc and motherboard nodes.
> -- 
> Julien Grall
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel