[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <90bc371d-a296-51b3-8b78-62106c9690de@oracle.com>
Date: Sat, 21 Jul 2018 17:25:54 -0400
From: Boris Ostrovsky <boris.ostrovsky@...cle.com>
To: "M. Vefa Bicakci" <m.v.b@...box.com>, linux-kernel@...r.kernel.org
Cc: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Juergen Gross <jgross@...e.com>,
xen-devel@...ts.xenproject.org, x86@...nel.org,
stable@...r.kernel.org
Subject: Re: [PATCH 2/2] xen/pv: Call get_cpu_address_sizes to set
x86_virt/phys_bits
On 07/21/2018 03:49 PM, M. Vefa Bicakci wrote:
> diff --git a/arch/x86/xen/enlighten_pv.c b/arch/x86/xen/enlighten_pv.c
> index 439a94bf89ad..87afb000142a 100644
> --- a/arch/x86/xen/enlighten_pv.c
> +++ b/arch/x86/xen/enlighten_pv.c
> @@ -1257,6 +1257,7 @@ asmlinkage __visible void __init xen_start_kernel(void)
>
> /* Work out if we support NX */
> get_cpu_cap(&boot_cpu_data);
> + get_cpu_address_sizes(&boot_cpu_data);
> x86_configure_nx();
Have you observed any problems without this call? get_cpu_cap() is only
called here to set X86_FEATURE_NX, and is then called again, together
with get_cpu_address_sizes(), from early_identify_cpu().
-boris
Powered by blists - more mailing lists