From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: [RFC 05/10] x86/speculation: Add basic IBRS support infrastructure Date: Wed, 24 Jan 2018 07:09:06 -0800 Message-ID: <68fc14f7-38b0-5127-5c7a-a11c27e3b166@linux.intel.com> References: <1516476182-5153-1-git-send-email-karahmed@amazon.de> <1516476182-5153-6-git-send-email-karahmed@amazon.de> <1516741116.13558.11.camel@infradead.org> <20180124084735.GM2228@hirez.programming.kicks-ass.net> <1516784541.13558.90.camel@infradead.org> <20180124091049.GB12100@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Peter Zijlstra , Thomas Gleixner , KarimAllah Ahmed , linux-kernel@vger.kernel.org, Andi Kleen , Andrea Arcangeli , Andy Lutomirski , Ashok Raj , Asit Mallick , Borislav Petkov , Dan Williams , Dave Hansen , "H . Peter Anvin" , Ingo Molnar , Janakarajan Natarajan , Joerg Roedel , Jun Nakajima , Laura Abbott , Linus Torvalds , Masami Hiramatsu , To: Greg Kroah-Hartman , David Woodhouse Return-path: In-Reply-To: <20180124091049.GB12100@kroah.com> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 1/24/2018 1:10 AM, Greg Kroah-Hartman wrote: > >> That means the whitelist ends up basically empty right now. Should I >> add a command line parameter to override it? Otherwise we end up having >> to rebuild the kernel every time there's a microcode release which >> covers a new CPU SKU (which is why I kind of hate the whitelist, but >> Arjan is very insistent...) > > Ick, no, whitelists are a pain for everyone involved. Don't do that > unless it is absolutely the only way it will ever work. > > Arjan, why do you think this can only be done as a whitelist? I suggested a minimum version list for those cpus that need it. microcode versions are tricky (and we've released betas etc etc with their own numbers) and as a result there might be several numbers that have those issues with their IBRS for the same F/M/S