[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <5B3A09EA02000078001CFBB7@prv1-mh.provo.novell.com>
Date: Mon, 02 Jul 2018 05:18:02 -0600
From: "Jan Beulich" <JBeulich@...e.com>
To: "Juergen Gross" <jgross@...e.com>
Cc: "the arch/x86 maintainers" <x86@...nel.org>, <tglx@...utronix.de>,
"xen-devel" <xen-devel@...ts.xenproject.org>,
"Boris Ostrovsky" <boris.ostrovsky@...cle.com>, <mingo@...hat.com>,
<linux-kernel@...r.kernel.org>, <stable@...r.kernel.org>,
<hpa@...or.com>
Subject: Re: [Xen-devel] [PATCH] xen: setup pv irq ops vector earlier
>>> 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.
Jan
Powered by blists - more mailing lists