From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: [RFC 05/10] x86/speculation: Add basic IBRS support infrastructure Date: Mon, 22 Jan 2018 10:51:53 +0100 Message-ID: <20180122095153.GB2228@hirez.programming.kicks-ass.net> References: <1516476182-5153-1-git-send-email-karahmed@amazon.de> <1516476182-5153-6-git-send-email-karahmed@amazon.de> <20180121145655.ddme3w6kzxthu6al@pd.tnic> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Thomas Gleixner , KarimAllah Ahmed , linux-kernel@vger.kernel.org, Andi Kleen , Andrea Arcangeli , Andy Lutomirski , Arjan van de Ven , Ashok Raj , Asit Mallick , Dan Williams , Dave Hansen , David Woodhouse , Greg Kroah-Hartman , "H . Peter Anvin" , Ingo Molnar , Janakarajan Natarajan , Joerg Roedel , Jun Nakajima , Laura Abbott , Linus Torvalds Return-path: Content-Disposition: inline In-Reply-To: <20180121145655.ddme3w6kzxthu6al@pd.tnic> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Sun, Jan 21, 2018 at 03:56:55PM +0100, Borislav Petkov wrote: > Also, blacklisting microcode for early loading will become an ugly dance > so I'd like to avoid it if possible. > > Thus, it would be much much easier if dracut/initrd creation thing > already filters those blacklisted blobs by looking at the revision in > the header. Which is much easier. That wouldn't be enough; AFAIU there's people with this stuff already flashed in their BIOS. So the kernel needs to deal with it one way or another.