[<prev] [next>] [day] [month] [year] [list]
Message-ID: <f6615f1c-6835-eba5-7b38-be06927700c9@suse.com>
Date: Mon, 2 Jul 2018 13:27:55 +0200
From: Juergen Gross <jgross@...e.com>
To: Jan Beulich <JBeulich@...e.com>
Cc: the arch/x86 maintainers <x86@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
xen-devel <xen-devel@...ts.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>, mingo@...hat.com,
lkml <linux-kernel@...r.kernel.org>, stable@...r.kernel.org,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [Xen-devel] [PATCH] xen: setup pv irq ops vector earlier
On 02/07/18 13:18, Jan Beulich wrote:
>>>> On 02.07.18 at 12:00, <jgross@...e.com> wrote:
>> --- a/arch/x86/xen/enlighten_pv.c
>> +++ b/arch/x86/xen/enlighten_pv.c
>> @@ -1213,6 +1213,7 @@ asmlinkage __visible void __init xen_start_kernel(void)
>> pv_info = xen_info;
>> pv_init_ops.patch = paravirt_patch_default;
>> pv_cpu_ops = xen_cpu_ops;
>> + xen_init_irq_ops();
>
> Isn't this still too late? xen_setup_machphys_mapping(), for example,
> has a WARN_ON(), which implies multiple printk()s.
Seems as if it would be a good idea to move calling
xen_setup_machphys_mapping() into xen_init_mmu_ops(). There is really
no need to do it earlier.
Juergen
Powered by blists - more mailing lists