From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751812AbeAZLpi (ORCPT ); Fri, 26 Jan 2018 06:45:38 -0500 Received: from mx1.redhat.com ([209.132.183.28]:41554 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751363AbeAZLph (ORCPT ); Fri, 26 Jan 2018 06:45:37 -0500 Message-ID: <1516967135.2801.1.camel@redhat.com> Subject: Re: [PATCH] x86/microcode/intel: print previous microcode revision during early update From: Petr Oros Reply-To: poros@redhat.com To: Borislav Petkov Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, linux-kernel@vger.kernel.org Date: Fri, 26 Jan 2018 12:45:35 +0100 In-Reply-To: <20180126104109.slxxoq4vkqytqjxd@pd.tnic> References: <20180126103451.16863-1-poros@redhat.com> <20180126104109.slxxoq4vkqytqjxd@pd.tnic> Organization: Red Hat Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Borislav Petkov píše v Pá 26. 01. 2018 v 11:41 +0100: > On Fri, Jan 26, 2018 at 11:34:50AM +0100, Petr Oros wrote: > > When kernel do early microcode update, code printing only > > new microcode version. But in this case we no have chance > > to check which version was in cpu from BIOS vendor. > > And we need that because? > During time of facing the Spectre vulnerability and the requirement of handling different microcode updates, it has shown, that it would be useful to have additional information which microcode version was in BIOS, if the early-update routine will apply an update.