[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v3 03/14] xen: arm: allocate dom0 memory separately from preparing the dtb
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? But maybe it is best to keep that separate. A "xen" node is somewhat analogous to a "soc" or "motherboard" node I guess. > "xen" { > #address-cells = 2; > #size-cells = 2; > memory { > ... > } > timer { > ... > } > } _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |