From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>
Subject: Re: [PATCH] arm: introduce a DTS for Xen unprivileged virtual machines
Date: Thu, 20 Sep 2012 15:11:56 +0100 [thread overview]
Message-ID: <alpine.DEB.2.02.1209201501140.29232@kaball.uk.xensource.com> (raw)
In-Reply-To: <201209201327.45802.arnd@arndb.de>
On Thu, 20 Sep 2012, Arnd Bergmann wrote:
> On Thursday 20 September 2012, Ian Campbell wrote:
> > On Thu, 2012-09-20 at 12:56 +0100, Stefano Stabellini wrote:
> > > On Thu, 20 Sep 2012, Ian Campbell wrote:
> > > > On Wed, 2012-09-19 at 18:44 +0100, Stefano Stabellini wrote:
>
> > > > > + compatible = "xen,xenvm-4.2", "arm,vexpress";
> > > >
> > > > Is this second compatible thing actually true? We don't actually emulate
> > > > much (anything?) of what would be on a real vexpress motherboard.
> > > >
> > > > "arm,vexpress" is used only in v2m.c and I don't think we want the
> > > > majority of that -- we don't provide any of the peripherals which it
> > > > registers.
> > > >
> > > > I think the only things we might want out of that lot are the arch timer
> > > > and perhaps the uart0 (as a debug port).
> > > >
> > > > I suspect we should have our own xen machine .c.
> > > >
> > > > [...]
> > >
> > > It is true that we are "arm,vexpress" compatible at the moment.
> >
> > But we aren't, we don't emulate 90%+ of the actual hardware which
> > vexpress compatibility would actually imply.
> >
> > Look in arch/arm/mach-vexpress/v2m.c, which is the only thing keyed off
> > this compat value -- it's full of stuff which we don't (and aren't going
> > to) implement.
>
> It's not much different in the end, but I think I'd rather make the
> compatible list in the device tree "xen,xenvm-4.2", "xen,xenvm" without
> listing "arm,vexpress", but then adding "xen,xenvm" to the list of
> compatible devices in the vexpress kernel code.
>
> The main difference is that if we decide to separate out the Linux
> code for Xen and vexpress later into distinct ports, we have the
> option to do that. vexpress will support multiplatform configurations
> in 3.7 anyway, so the idea of making all virtual platforms part of
> vexpress in order to be able to boot the same kernel on them is not
> all that important any more.
That's a very good idea, I'll do that.
next prev parent reply other threads:[~2012-09-20 14:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 17:44 Stefano Stabellini
2012-09-20 10:06 ` Pawel Moll
2012-09-20 11:18 ` Dave Martin
2012-09-20 12:02 ` Stefano Stabellini
2012-09-20 21:29 ` Konrad Rzeszutek Wilk
2012-09-21 11:17 ` Stefano Stabellini
2012-09-20 11:39 ` Stefano Stabellini
2012-09-20 11:55 ` Pawel Moll
2012-09-20 12:15 ` Stefano Stabellini
2012-09-20 12:28 ` Marc Zyngier
2012-09-20 13:30 ` Ian Campbell
2012-09-20 13:50 ` Marc Zyngier
2012-09-20 10:17 ` Ian Campbell
2012-09-20 11:56 ` Stefano Stabellini
2012-09-20 12:18 ` Ian Campbell
2012-09-20 12:39 ` Stefano Stabellini
2012-09-20 13:16 ` Ian Campbell
2012-09-20 13:27 ` Arnd Bergmann
2012-09-20 14:11 ` Stefano Stabellini [this message]
2012-09-20 14:24 ` Pawel Moll
2012-09-20 10:45 ` [Xen-devel] " David Vrabel
2012-09-20 11:21 ` Dave Martin
2012-09-20 12:04 ` Stefano Stabellini
2012-09-20 12:57 ` Dave Martin
2012-09-20 12:00 ` Stefano Stabellini
2012-09-20 20:26 ` Rob Herring
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=alpine.DEB.2.02.1209201501140.29232@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=arnd@arndb.de \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®