All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: ian.campbell@citrix.com, 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: Thu, 24 Oct 2013 17:30:55 +0100	[thread overview]
Message-ID: <52694B3F.5090008@linaro.org> (raw)
In-Reply-To: <20131024144921.GB29944@phenom.dumpdata.com>



On 10/24/2013 03:49 PM, Konrad Rzeszutek Wilk wrote:
> On Wed, Oct 23, 2013 at 11:08:01PM +0100, Julien Grall wrote:
>>
>>
>> On 10/23/2013 05:15 PM, Konrad Rzeszutek Wilk wrote:
>>> On Sun, Oct 06, 2013 at 09:52:40PM +0100, Julien Grall wrote:
>> Actually, I looked closer the code, with the new solution
>> xen_raw_printk/xen_raw_console_write can't be call on ARM during
>> early init.
>>
>> On ARM, xen_domain_type is initialized during a core initcall. So
>> it's not possible to call the function before.
>
> OK, so won't work and won't harm. That is OK I think.

I use xen_raw_printk every time to debug early code and when someone has 
an issue with Linux (for instance no log in the console), we advise them 
to use xen_raw_printk.
It's annoying for every ARM developer to modify ourself the function 
each time we need it...

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.

So I think, for now the best solution is to call unconditionally 
dom0_write_console on ARM (32 and 64 bits).

#ifdef CONFIG_X86
if (xen_domain) {
   ...
} else if (...) {
...
}
#else
    dom0_write_console
#endif

It will avoid to carry non-upstream patch for ARM and point out every 
time developer to this patch.

Stefano, Ian, any opinion?

-- 
Julien Grall

  parent reply	other threads:[~2013-10-24 16:30 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-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             ` Julien Grall [this message]
2013-10-24 16:43               ` [Xen-devel] " Ian Campbell
2013-10-25 19:38                 ` Konrad Rzeszutek Wilk
2013-10-26  8:27                   ` Ian Campbell
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-25 19:38                 ` Konrad Rzeszutek Wilk
2013-10-24 16:43               ` Ian Campbell
2013-10-23 16:15       ` Konrad Rzeszutek Wilk
2013-10-06 20:52     ` Julien Grall
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=52694B3F.5090008@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=ian.campbell@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --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.