[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1348142133.11116.109.camel@hornet>
Date: Thu, 20 Sep 2012 12:55:33 +0100
From: Pawel Moll <pawel.moll@....com>
To: Stefano Stabellini <stefano.stabellini@...citrix.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ian Campbell <Ian.Campbell@...rix.com>,
"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
"konrad.wilk@...cle.com" <konrad.wilk@...cle.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] arm: introduce a DTS for Xen unprivileged virtual
machines
On Thu, 2012-09-20 at 12:39 +0100, Stefano Stabellini wrote:
> There are no peripherals apart from the ones that are already described
> here (timer, gic). All the peripherals that the guest sees are virtual
> devices that show up on xenbus (a virtual bus). In order to initialize
> 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@...00000 and gic@...01000. The rest (not much of it ;-) is a
"generic A15 platform".
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 better
off with generating this stuff in runtime, by whatever tool is used to
instantiate the guest?
Paweł
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists