[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <da2e8c6b-c04a-2743-e896-2e4a39a611e2@intel.com>
Date: Tue, 9 Jan 2018 17:51:50 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>
Cc: Linus Torvalds <torvalds@...uxfoundation.org>, x86@...nel.org,
Peter Zijlstra <peterz@...radead.org>,
Borislav Petkov <bp@...en8.de>,
David Woodhouse <dwmw@...zon.co.uk>,
Tim Chen <tim.c.chen@...ux.intel.com>,
Andrea Arcangeli <aarcange@...hat.com>,
Andi Kleen <ak@...ux.intel.com>,
Greg KH <gregkh@...uxfoundation.org>,
Andy Lutomirski <luto@...nel.org>,
Arjan Van De Ven <arjan.van.de.ven@...el.com>
Subject: Re: [patch RFC 3/5] x86/spectre: Prepare for IBRS selection
On 01/09/2018 05:06 PM, Thomas Gleixner wrote:
...
> + case SPECTRE_V2_CMD_RETPOLINE:
> + if (IS_ENABLED(CONFIG_RETPOLINE))
> + goto retpoline_auto;
> + break;
> + }
> + pr_err("kernel not compiled with retpoline; no mitigation available!");
> + return;
> +
> +retpoline_auto:
> + /*
> + * Note: This only takes effect during boot before alternatives
> + * have been patched. Later invocations after late micro code
> + * update wont change the boot selection even if IBRS has not been
> + * made available by the microcode loading.
> + */
> if (boot_cpu_data.x86_vendor == X86_VENDOR_AMD) {
> retpoline_amd:
Should the "IBRS has not been" be "IBRS has been"?
Powered by blists - more mailing lists