[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b57092b4-e740-e1f8-3885-a817bb7d4e70@arm.com>
Date: Tue, 27 Feb 2018 11:14:23 +0000
From: Julien Grall <julien.grall@....com>
To: Juergen Gross <jgross@...e.com>,
Andrii Anisov <andrii_anisov@...m.com>,
linux-kernel@...r.kernel.org, xen-devel@...ts.xenproject.org
Cc: boris.ostrovsky@...cle.com,
Stefano Stabellini <sstabellini@...nel.org>, jbeulich@...e.com
Subject: Re: [Xen-devel] [PATCH] xen: use hvc console for dom0
Hi,
On 26/02/18 12:32, Juergen Gross wrote:
> On 26/02/18 13:06, Andrii Anisov wrote:
>> Hello Juergen,
>>
>>
>> On 26.02.18 13:08, Juergen Gross wrote:
>>> Today the hvc console is added as a preferred console for pv domUs
>>> only. As this requires a boot parameter for getting dom0 messages per
>>> default add it for dom0, too.
>>>
>>> Signed-off-by: Juergen Gross <jgross@...e.com>
>>> ---
>>> arch/x86/xen/enlighten_pv.c | 4 +++-
>>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/arch/x86/xen/enlighten_pv.c b/arch/x86/xen/enlighten_pv.c
>> Is this something x86 specific? Could it be a generic approach?
>
> In case ARM wants something similar I guess the test for
> xen_initial_domain() should be dropped in xen_early_init().
I am pretty sure we discussed to remove !xen_initial_domain() for Arm in
the past. But I don't remember why the patch was not sent to remove it.
Anyway, I guess this should be fine to have hvc as a preferred console
for the initial domain as well.
Cheers,
--
Julien Grall
Powered by blists - more mailing lists