All of lore.kernel.org
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: introduce a DTS for Xen unprivileged virtual machines
Date: Thu, 20 Sep 2012 13:28:48 +0100	[thread overview]
Message-ID: <505B0C00.5010003@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1209201308490.29232@kaball.uk.xensource.com>

On 20/09/12 13:15, Stefano Stabellini wrote:
> On Thu, 20 Sep 2012, Pawel Moll wrote:
>> 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?
> 
> Yes, it is certainly going to be generated at run time. Does it make
> sense to keep an example under arch/arm/boot/dts? I think so. There must
> be other platforms that actually pass the device tree to the kernel from
> the firmware and still have a dts in the kernel tree, right?
> If actually there are none, it is probably best to forget about this
> patch :)
> 
> Regarding the choice of "arm,vexpress", there was a discussion at kernel
> summit about vexpress being the right choice as a base platform for
> virtual machines on ARM, even though in the Xen case it means having a
> vexpress with no peripherals.

I think the important thing here is that the memory map is RS1. As this
is a (very limited) subset of a vexpress A15, it seems to make some sense.

I still think it is useful at have an example of such a platform in the
tree, if only as a very minimal example.

	M.
-- 
Jazz is not dead. It just smells funny...

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <marc.zyngier@arm.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Pawel Moll <Pawel.Moll@arm.com>,
	"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>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] arm: introduce a DTS for Xen unprivileged virtual machines
Date: Thu, 20 Sep 2012 13:28:48 +0100	[thread overview]
Message-ID: <505B0C00.5010003@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1209201308490.29232@kaball.uk.xensource.com>

On 20/09/12 13:15, Stefano Stabellini wrote:
> On Thu, 20 Sep 2012, Pawel Moll wrote:
>> 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?
> 
> Yes, it is certainly going to be generated at run time. Does it make
> sense to keep an example under arch/arm/boot/dts? I think so. There must
> be other platforms that actually pass the device tree to the kernel from
> the firmware and still have a dts in the kernel tree, right?
> If actually there are none, it is probably best to forget about this
> patch :)
> 
> Regarding the choice of "arm,vexpress", there was a discussion at kernel
> summit about vexpress being the right choice as a base platform for
> virtual machines on ARM, even though in the Xen case it means having a
> vexpress with no peripherals.

I think the important thing here is that the memory map is RS1. As this
is a (very limited) subset of a vexpress A15, it seems to make some sense.

I still think it is useful at have an example of such a platform in the
tree, if only as a very minimal example.

	M.
-- 
Jazz is not dead. It just smells funny...


  reply	other threads:[~2012-09-20 12:28 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
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 [this message]
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=505B0C00.5010003@arm.com \
    --to=marc.zyngier@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.