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: Mon, 28 Oct 2013 11:48:37 -0400 [thread overview]
Message-ID: <20131028154837.GC4353@phenom.dumpdata.com> (raw)
In-Reply-To: <1382776028.22417.174.camel@hastur.hellion.org.uk>
On Sat, Oct 26, 2013 at 09:27:08AM +0100, Ian Campbell wrote:
> On Fri, 2013-10-25 at 15:38 -0400, Konrad Rzeszutek Wilk wrote:
> > On Thu, Oct 24, 2013 at 05:43:54PM +0100, Ian Campbell wrote:
> > > 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.
>
> Does earlyprintk=ttyS0,cough not Just Work for HVM guests? That would
> avoid all of this stuff and assuming it works would be preferable IMHO.
It works OK. But this is an alternative avenue of using 'xen_raw_printk'
for both PV and HVM.
>
> Anyway, if not, then given that the xen_cpuid_base case is entirely x86
> specific perhaps we can abstract this as something like:
>
> if (xen_arch_raw_console(str))
> return
>
> dom0_write_console(...)
>
> Then ARM:
> #define xen_arch_raw_console 0
> and x86
> static inline int xen_arch_raw_console(str)
> {
> if (xen_domain())
> return 0;
>
> /* Do the outb thing */
> return 1;
> }
>
> This would also avoid the need for #ifdef x86 in the main function which
> Julien pointed out.
OK.
>
> Ian.
>
next prev parent reply other threads:[~2013-10-28 15:48 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 ` Julien Grall
2013-09-27 21:49 ` [Xen-devel] " Julien Grall
2013-09-30 14:45 ` Konrad Rzeszutek Wilk
2013-09-30 14:45 ` [Xen-devel] " Konrad Rzeszutek Wilk
2013-10-06 20:52 ` 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 14:49 ` [Xen-devel] " Konrad Rzeszutek Wilk
2013-10-24 16:30 ` Julien Grall
2013-10-24 16:30 ` [Xen-devel] " 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 ` [Xen-devel] " Konrad Rzeszutek Wilk
2013-10-26 8:27 ` Ian Campbell
2013-10-28 15:48 ` Konrad Rzeszutek Wilk
2013-10-28 15:48 ` Konrad Rzeszutek Wilk [this message]
2013-10-26 8:27 ` Ian Campbell
2013-10-23 16:15 ` Konrad Rzeszutek Wilk
2013-10-06 20:52 ` 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=20131028154837.GC4353@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.