From: ian.campbell@citrix•com (Ian Campbell)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 3/3] xen/arm: allow console=hvc0 to be omitted for guests
Date: Fri, 27 Feb 2015 09:34:59 +0000 [thread overview]
Message-ID: <1425029699.14641.114.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1502261817210.23507@kaball.uk.xensource.com>
On Thu, 2015-02-26 at 18:22 +0000, Stefano Stabellini wrote:
> On Wed, 18 Feb 2015, Ian Campbell wrote:
> > On Wed, 2015-02-18 at 09:50 -0600, Rob Herring wrote:
> > > On Wed, Feb 18, 2015 at 7:51 AM, Julien Grall <julien.grall@linaro•org> wrote:
> > > > From: Ard Biesheuvel <ard.biesheuvel@linaro•org>
> > > >
> > > > This patch registers hvc0 as the preferred console if no console
> > > > has been specified explicitly on the kernel command line.
> > > >
> > > > The purpose is to allow platform agnostic kernels and boot images
> > > > (such as distro installers) to boot in a Xen/ARM domU without the
> > > > need to modify the command line by hand.
> > >
> > > How does this interact with DT chosen stdout-path?
> >
> > I think it shouldn't any more than the existing calls from e.g. the 8250
> > driver to preferred_console do.
> >
> > > Is there a node for hvc0?
> >
> > Not a direct one, it is inferred from the presence of the general Xen
> > node.
>
> Xen PV consoles, including hvc0, as all the other Xen PV devices are
> advertised on xenstore.
Do we actually use the xenstore node for hvc0? I thought we got it from
hvmparams (so the primary it can be used before xenstore is up)
>
>
> > I did vaguely consider handling a stdout-path pointing to that --
> > but it seemed a bit of an abuse.
>
next prev parent reply other threads:[~2015-02-27 9:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 13:51 [PATCH v2 0/3] arm/arm64: Detect Xen support earlier Julien Grall
2015-02-18 13:51 ` [PATCH v2 1/3] arm/xen: Correctly check if the event channel interrupt is present Julien Grall
2015-02-26 18:08 ` Stefano Stabellini
2015-02-18 13:51 ` [PATCH v2 2/3] arm,arm64/xen: move Xen initialization earlier Julien Grall
2015-04-07 17:26 ` Stefano Stabellini
2015-05-06 14:04 ` Stefano Stabellini
2015-02-18 13:51 ` [PATCH v2 3/3] xen/arm: allow console=hvc0 to be omitted for guests Julien Grall
2015-02-18 15:25 ` Ian Campbell
2015-02-18 15:50 ` Rob Herring
2015-02-18 16:03 ` Ian Campbell
2015-02-26 18:22 ` Stefano Stabellini
2015-02-27 9:34 ` Ian Campbell [this message]
2015-02-27 9:47 ` Stefano Stabellini
2015-02-25 16:22 ` [PATCH v2 0/3] arm/arm64: Detect Xen support earlier Julien Grall
2015-02-25 16:34 ` Will Deacon
2015-02-25 16:38 ` Julien Grall
2015-02-25 16:40 ` [Xen-devel] " Ian Campbell
2015-02-25 18:01 ` Will Deacon
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=1425029699.14641.114.camel@citrix.com \
--to=ian.campbell@citrix$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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