From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Dave Martin <dave.martin@linaro.org>,
Pawel Moll <pawel.moll@arm.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH] arm: introduce a DTS for Xen unprivileged virtual machines
Date: Fri, 21 Sep 2012 12:17:15 +0100 [thread overview]
Message-ID: <alpine.DEB.2.02.1209211214520.29232@kaball.uk.xensource.com> (raw)
In-Reply-To: <20120920212948.GF27312@konrad-lan.dumpdata.com>
On Thu, 20 Sep 2012, Konrad Rzeszutek Wilk wrote:
> On Thu, Sep 20, 2012 at 12:18:15PM +0100, Dave Martin wrote:
> > On Thu, Sep 20, 2012 at 11:06:03AM +0100, Pawel Moll wrote:
> > > Morning,
> > >
> > > On Wed, 2012-09-19 at 18:44 +0100, Stefano Stabellini wrote:
> > > > +/dts-v1/;
> > > > +
> > > > +/include/ "skeleton.dtsi"
> > >
> > > Any particular reason to include skeleton? And I think it would be
> > > better to use #address-cells = <2> and #size-cells = <2>, to be ready
> > > for LPAE addresses...
> > >
> > > > +/ {
> > > > + model = "XENVM-4.2";
> > > > + compatible = "xen,xenvm-4.2", "arm,vexpress";
> > > > + interrupt-parent = <&gic>;
> > > > +
> > > > + chosen {
> > > > + bootargs = "earlyprintk console=hvc0 root=/dev/xvda init=/sbin/init";
>
> earlyprintk=xen ?
>
earlyprintk is not "selectable" on ARM (that would be a nice addition
though). It just goes to the configured uart, that is the only piece of
hardware that is being emulated by Xen at the moment.
In any case I have removed anything debug related, including
earlyprintk, from the default bootargs.
next prev parent reply other threads:[~2012-09-21 11:18 UTC|newest]
Thread overview: 27+ 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-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 [this message]
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
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.1209211214520.29232@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=dave.martin@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).