mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
	Pawel Moll <pawel.moll@arm.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 13:39:58 +0100	[thread overview]
Message-ID: <alpine.DEB.2.02.1209201333460.29232@kaball.uk.xensource.com> (raw)
In-Reply-To: <1348143533.26501.28.camel@zakaz.uk.xensource.com>

On Thu, 20 Sep 2012, Ian Campbell wrote:
> > Versatile Express is flexible enough to be a good base for our own
> > virtual machine platform, especially if the maintainers keep an eye on
> > getting everything through DT and not expecting devices just to be there
> > ;-)
> 
> Perhaps what we want is a stricter subset of the stuff in mach-vexpress
> then. But if so then this should be expressed both in the DT and in the
> code, not just papered over by declaring things compatible when they are
> not.

But it is already expressed in the DT, by removing all the device nodes
we don't emulated. And it is already expressed in the code, by fully
discovering peripherals via DT, therefore not trying to initialize
non-present devices.


> > > > +	gic: interrupt-controller@2c001000 {
> > > > +		compatible = "arm,cortex-a9-gic";
> > > 
> > > Don't we mean "arm,cortex-a15-gic" here? That's what we actually
> > > provide. I'm not sure how the a9 and a15 differ.
> > 
> > The GIC that comes with vexpress is a9 compatible.
> 
> The GIC which Xen emulates is the one which matters here though, and
> that is an a15.

The a15 gic is still a9 compatible. OK to be precise I am going to add
"arm,cortex-a15-gic", but I cannot really remove "arm,cortex-a9-gic".

  reply	other threads:[~2012-09-20 12:40 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 [this message]
2012-09-20 13:16         ` Ian Campbell
2012-09-20 13:27       ` Arnd Bergmann
2012-09-20 14:11         ` Stefano Stabellini
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.1209201333460.29232@kaball.uk.xensource.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --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®