linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: julien.grall@arm.com (Julien Grall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/5] Xen: Select correct dom0 console
Date: Mon, 16 Jan 2017 12:43:58 +0000	[thread overview]
Message-ID: <063e6a8d-2d1e-d88e-7a38-a2f9d992813e@arm.com> (raw)
In-Reply-To: <20170103172859.GC14183@leverpostej>

Hi Mark,

On 03/01/17 17:29, Mark Rutland wrote:
> On Thu, Dec 15, 2016 at 12:27:17PM +0000, Andre Przywara wrote:
>> From: Ian Campbell <ian.campbell@citrix.com>
>>
>> If Xen is enabled, tell Dom0 to use the 'hvc0' console, and fall back to
>> the usual ttyAMA0 otherwise.
>>
>> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
>> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
>> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
>> Reviewed-by: Julien Grall <julien.grall@arm.com>
>> Tested-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>> ---
>>  configure.ac | 3 ++-
>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/configure.ac b/configure.ac
>> index ea02dca..d23cced 100644
>> --- a/configure.ac
>> +++ b/configure.ac
>> @@ -105,7 +105,8 @@ AC_ARG_WITH([initrd],
>>  AC_SUBST([FILESYSTEM], [$USE_INITRD])
>>  AM_CONDITIONAL([INITRD], [test "x$USE_INITRD" != "x"])
>>
>> -C_CMDLINE="console=ttyAMA0 earlyprintk=pl011,0x1c090000"
>> +AS_IF([test "x$X_IMAGE" = "x"],[C_CONSOLE="ttyAMA0"],[C_CONSOLE="hvc0"])
>> +C_CMDLINE="console=$C_CONSOLE earlyprintk=pl011,0x1c090000"
>
> Just to check: what happesns if Dom0 tries to write to 0x1c090000?

Xen is emulating a simple UART (only write is supported) replacing the 
real UART for DOM0. So character will be printed on the console when the 
domain is writing to 0x1c090000.

>
> Shouldn't we override/delete earlyprintk/earlycon here too?

The ideal would be to use xen console for the earlyprintk/earlycon, but 
it seems that it has not been wired for ARM.

So for now, I would keep the earlyprintk options to help developer 
debugging early crash.

> I've applied this as-is, so if we do need to, I'll need a fixup patch.

Thank you for pushing the series.

Cheers,

-- 
Julien Grall

  reply	other threads:[~2017-01-16 12:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-15 12:27 [PATCH v3 0/5] boot-wrapper: arm64: Xen support Andre Przywara
2016-12-15 12:27 ` [PATCH v3 1/5] configure: fix file detection when cross-compiling Andre Przywara
2016-12-15 12:27 ` [PATCH v3 2/5] Support for building in a Xen binary Andre Przywara
2016-12-15 12:27 ` [PATCH v3 3/5] Xen: Support adding DT nodes Andre Przywara
2016-12-15 12:27 ` [PATCH v3 4/5] Xen: Select correct dom0 console Andre Przywara
2017-01-03 17:29   ` Mark Rutland
2017-01-16 12:43     ` Julien Grall [this message]
2016-12-15 12:27 ` [PATCH v3 5/5] Explicitly clean linux-system.axf and xen-system.axf Andre Przywara
2017-01-03 17:32 ` [PATCH v3 0/5] boot-wrapper: arm64: Xen support Mark Rutland

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=063e6a8d-2d1e-d88e-7a38-a2f9d992813e@arm.com \
    --to=julien.grall@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).