From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pawel Moll Subject: Re: [PATCH] arm: introduce a DTS for Xen unprivileged virtual machines Date: Thu, 20 Sep 2012 12:55:33 +0100 Message-ID: <1348142133.11116.109.camel@hornet> References: <1348076658-4511-1-git-send-email-stefano.stabellini@eu.citrix.com> <1348135563.11116.94.camel@hornet> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Stefano Stabellini Cc: "linux-kernel@vger.kernel.org" , Ian Campbell , "xen-devel@lists.xensource.com" , "konrad.wilk@oracle.com" , "linux-arm-kernel@lists.infradead.org" List-Id: xen-devel@lists.xenproject.org On Thu, 2012-09-20 at 12:39 +0100, Stefano Stabellini wrote: > There are no peripherals apart from the ones that are already describ= ed > here (timer, gic). All the peripherals that the guest sees are virtua= l > devices that show up on xenbus (a virtual bus). In order to initializ= e > xenbus, the guest only needs the hypervisor node. So I'll remove the > ranges and interrupt-map. So all the peripherals are actually discoverable - awesome! But the fact is that the only "vexpressness" of this tree is memory@80000000 and gic@2c001000. The rest (not much of it ;-) is a "generic A15 platform".=20 I understand that you had to use some "compatible" value to get initialization code and I'm flattered ;-) by your choice of "arm,vexpress", but maybe - as suggested by others - you would be bette= r off with generating this stuff in runtime, by whatever tool is used to instantiate the guest? Pawe=C5=82