All of lore.kernel.org
 help / color / mirror / Atom feed
From: julien.grall@linaro.org (Julien Grall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] xen/arm: allow console=hvc0 to be omitted for guests
Date: Tue, 10 Feb 2015 15:36:32 +0800	[thread overview]
Message-ID: <54D9B500.2010600@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1502100648050.29696@kaball.uk.xensource.com>

Hi Stefano,

On 10/02/2015 15:00, Stefano Stabellini wrote:
> On Fri, 30 Jan 2015, Ard Biesheuvel wrote:
>> 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.
>>
>> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> ---
>>
>> This applies on top of the patch Julien is cooking up to move the
>> call to xen_guest_init() to an earlier boot stage. This needs to
>> be at least before the call to console_init() in start_kernel()
>> for this patch to do anything meaningful.
>
> This patch looks good but there isn't much point in queuing this up
> without the prerequisite.
>
> Julien, what patch exactly is that? What is the status of it?

Calling xen_guest_init from setup_arch. It's based on a patch you sent 
an year ago (http://osdir.com/ml/linux-kernel/2013-08/msg00675.html)

But I had some issue with the console. The splitting of xen_guest_init 
doesn't work. It seems that we decode the IRQ too early.

I haven't had time to rework it and sent it.

Regards,

-- 
Julien Grall

  parent reply	other threads:[~2015-02-10  7:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30 13:58 [PATCH] xen/arm: allow console=hvc0 to be omitted for guests Ard Biesheuvel
2015-02-10  7:00 ` Stefano Stabellini
2015-02-10  7:26   ` Ian Campbell
2015-02-10  7:51     ` Ard Biesheuvel
2015-02-10  7:51       ` Ard Biesheuvel
2015-02-10  8:59       ` Ian Campbell
2015-02-10  8:59       ` Ian Campbell
2015-02-12  4:35         ` Stefano Stabellini
2015-02-12  4:52           ` Stefano Stabellini
2015-02-12  4:52           ` Stefano Stabellini
2015-02-12  4:54           ` Ian Campbell
2015-02-12  4:54           ` Ian Campbell
2015-02-12  5:20             ` Julien Grall
2015-02-12  6:12               ` Stefano Stabellini
2015-02-12  6:12               ` Stefano Stabellini
2015-02-12  5:20             ` Julien Grall
2015-02-12  4:35         ` Stefano Stabellini
2015-02-10  7:26   ` Ian Campbell
2015-02-10  7:36   ` Julien Grall [this message]
2015-02-10  7:36   ` Julien Grall
2015-02-10  7:00 ` Stefano Stabellini
  -- strict thread matches above, loose matches on Subject: below --
2015-01-30 13:58 Ard Biesheuvel

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=54D9B500.2010600@linaro.org \
    --to=julien.grall@linaro.org \
    --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 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.