From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: introduce a DTS for Xen unprivileged virtual machines
Date: Thu, 20 Sep 2012 12:55:33 +0100 [thread overview]
Message-ID: <1348142133.11116.109.camel@hornet> (raw)
In-Reply-To: <alpine.DEB.2.02.1209201235450.29232@kaball.uk.xensource.com>
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 at 80000000 and gic at 2c001000. 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?
WARNING: multiple messages have this Message-ID (diff)
From: Pawel Moll <pawel.moll@arm.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm: introduce a DTS for Xen unprivileged virtual machines
Date: Thu, 20 Sep 2012 12:55:33 +0100 [thread overview]
Message-ID: <1348142133.11116.109.camel@hornet> (raw)
In-Reply-To: <alpine.DEB.2.02.1209201235450.29232@kaball.uk.xensource.com>
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@80000000 and gic@2c001000. 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ł
next prev parent reply other threads:[~2012-09-20 11:55 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 17:44 [PATCH] arm: introduce a DTS for Xen unprivileged virtual machines Stefano Stabellini
2012-09-19 17:44 ` Stefano Stabellini
2012-09-20 10:06 ` Pawel Moll
2012-09-20 10:06 ` Pawel Moll
2012-09-20 11:18 ` Dave Martin
2012-09-20 11:18 ` Dave Martin
2012-09-20 12:02 ` Stefano Stabellini
2012-09-20 12:02 ` Stefano Stabellini
2012-09-20 21:29 ` Konrad Rzeszutek Wilk
2012-09-20 21:29 ` Konrad Rzeszutek Wilk
2012-09-21 11:17 ` Stefano Stabellini
2012-09-21 11:17 ` Stefano Stabellini
2012-09-20 11:39 ` Stefano Stabellini
2012-09-20 11:39 ` Stefano Stabellini
2012-09-20 11:55 ` Pawel Moll [this message]
2012-09-20 11:55 ` Pawel Moll
2012-09-20 12:15 ` Stefano Stabellini
2012-09-20 12:15 ` Stefano Stabellini
2012-09-20 12:15 ` Stefano Stabellini
2012-09-20 12:28 ` Marc Zyngier
2012-09-20 12:28 ` Marc Zyngier
2012-09-20 13:30 ` Ian Campbell
2012-09-20 13:30 ` Ian Campbell
2012-09-20 13:50 ` Marc Zyngier
2012-09-20 13:50 ` Marc Zyngier
2012-09-20 10:17 ` Ian Campbell
2012-09-20 10:17 ` Ian Campbell
2012-09-20 11:56 ` Stefano Stabellini
2012-09-20 11:56 ` Stefano Stabellini
2012-09-20 12:18 ` Ian Campbell
2012-09-20 12:18 ` Ian Campbell
2012-09-20 12:39 ` Stefano Stabellini
2012-09-20 12:39 ` Stefano Stabellini
2012-09-20 13:16 ` Ian Campbell
2012-09-20 13:16 ` Ian Campbell
2012-09-20 13:27 ` Arnd Bergmann
2012-09-20 13:27 ` Arnd Bergmann
2012-09-20 14:11 ` Stefano Stabellini
2012-09-20 14:11 ` Stefano Stabellini
2012-09-20 14:24 ` Pawel Moll
2012-09-20 14:24 ` Pawel Moll
2012-09-20 14:24 ` Pawel Moll
2012-09-20 10:45 ` [Xen-devel] " David Vrabel
2012-09-20 10:45 ` David Vrabel
2012-09-20 10:45 ` David Vrabel
2012-09-20 11:21 ` Dave Martin
2012-09-20 11:21 ` Dave Martin
2012-09-20 12:04 ` Stefano Stabellini
2012-09-20 12:04 ` Stefano Stabellini
2012-09-20 12:57 ` Dave Martin
2012-09-20 12:57 ` Dave Martin
2012-09-20 12:00 ` Stefano Stabellini
2012-09-20 12:00 ` Stefano Stabellini
2012-09-20 20:26 ` Rob Herring
2012-09-20 20:26 ` Rob Herring
2012-09-21 11:14 ` Stefano Stabellini
2012-09-21 11:14 ` Stefano Stabellini
2012-09-21 11:14 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1348142133.11116.109.camel@hornet \
--to=pawel.moll@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.