From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Julien Grall <julien.grall@linaro.org>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] [PATCH] xen/hvc-console: Make it work with HVM guests.
Date: Fri, 25 Oct 2013 15:38:12 -0400 [thread overview]
Message-ID: <20131025193812.GA6256@phenom.dumpdata.com> (raw)
In-Reply-To: <1382633034.22417.121.camel@hastur.hellion.org.uk>
On Thu, Oct 24, 2013 at 05:43:54PM +0100, Ian Campbell wrote:
> On Thu, 2013-10-24 at 17:30 +0100, Julien Grall wrote:
>
> > I'm sure the solution "move xen call earlier" will come up in few mails,
> > so there was a discussion for swiotlb few weeks ago
> > (https://lkml.org/lkml/2013/8/29/609). And the final decision was to
> > avoid specific Xen call in arch_setup.
>
> It wasn't so much a hard reject as a preference based on the need
> presented at the time.
>
> Perhaps a generic DT driven mechanism to detect hypervisors, called
> early, would be more acceptable?
>
> > Stefano, Ian, any opinion?
>
> The ifdef approach is a bit ugly, but if the other option doesn't work
> out I suppose we can live with it.
>
> But stepping back how/why is this function called on x86 when not
> running under Xen? Wouldn't the use have to be using console=hvc or
> earlyprintk=xen or something -- which strikes me as user error... IOW
> can we not just nuke the check
It shouldn't - ever. On x86 it is called from the early PV bootup code.
I occasionaly use it when developing/debugging and as such want it working
in HVM even during early bootup.
>
> Ian.
>
next prev parent reply other threads:[~2013-10-25 19:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 21:25 [PATCH] xen/hvc-console: Make it work with HVM guests Konrad Rzeszutek Wilk
2013-09-27 21:49 ` [Xen-devel] " Julien Grall
2013-09-30 14:45 ` Konrad Rzeszutek Wilk
2013-10-06 20:52 ` Julien Grall
2013-10-06 20:52 ` [Xen-devel] " Julien Grall
2013-10-23 16:15 ` Konrad Rzeszutek Wilk
2013-10-23 22:08 ` Julien Grall
2013-10-23 22:08 ` [Xen-devel] " Julien Grall
2013-10-24 14:49 ` Konrad Rzeszutek Wilk
2013-10-24 16:30 ` Julien Grall
2013-10-24 16:43 ` Ian Campbell
2013-10-24 16:43 ` [Xen-devel] " Ian Campbell
2013-10-25 19:38 ` Konrad Rzeszutek Wilk
2013-10-25 19:38 ` Konrad Rzeszutek Wilk [this message]
2013-10-26 8:27 ` [Xen-devel] " Ian Campbell
2013-10-28 15:48 ` Konrad Rzeszutek Wilk
2013-10-28 15:48 ` [Xen-devel] " Konrad Rzeszutek Wilk
2013-10-26 8:27 ` Ian Campbell
2013-10-24 16:30 ` Julien Grall
2013-10-24 14:49 ` Konrad Rzeszutek Wilk
2013-10-23 16:15 ` Konrad Rzeszutek Wilk
2013-09-30 14:45 ` Konrad Rzeszutek Wilk
2013-09-27 21:49 ` Julien Grall
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=20131025193812.GA6256@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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.