From mboxrd@z Thu Jan  1 00:00:00 1970
From: Julien Grall <julien.grall@linaro.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
Message-ID: <5280CCBB.4090008@linaro.org>
References: <1383842678.3189.15.camel@kazak.uk.xensource.com>
	<1383842696-8598-3-git-send-email-ian.campbell@citrix.com>
	<527C9043.1050702@linaro.org>
	<1383903402.3189.44.camel@kazak.uk.xensource.com>
	<5280C8A1.6050006@linaro.org>
	<1384171931.8909.47.camel@kazak.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <1384171931.8909.47.camel@kazak.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.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
List-Id: xen-devel@lists.xenproject.org

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