From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [Xen-devel] [PATCH] arm: introduce a DTS for Xen unprivileged virtual machines Date: Thu, 20 Sep 2012 11:45:57 +0100 Message-ID: <505AF3E5.1050306@citrix.com> References: <1348076658-4511-1-git-send-email-stefano.stabellini@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1348076658-4511-1-git-send-email-stefano.stabellini@eu.citrix.com> Sender: linux-kernel-owner@vger.kernel.org To: Stefano Stabellini Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com, Ian.Campbell@citrix.com, Pawel Moll , konrad.wilk@oracle.com, linux-arm-kernel@lists.infradead.org List-Id: xen-devel@lists.xenproject.org On 19/09/12 18:44, Stefano Stabellini wrote: > --- /dev/null > +++ b/arch/arm/boot/dts/vexpress-xenvm-4.2.dts Does this make sense? There is no fixed configuration for VMs. Is the intention to pass a DTS to the toolstack for it to create the VM with the appropriate amount of memory and peripheral mapped to the right place etc? Or is the toolstack going to create the VM and generate the DTB from (e.g.,) an xl VM configuration file. > + > + hypervisor { > + compatible = "xen,xen-4.2", "xen,xen"; > + reg = <0xb0000000 0x20000>; > + interrupts = <1 15 0xf08>; > + }; This node needs to be generated by the toolstack as only it knows what ABI the hypervisor has. David