From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751789AbeAZL6N (ORCPT ); Fri, 26 Jan 2018 06:58:13 -0500 Received: from mail.skyhub.de ([5.9.137.197]:56868 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751457AbeAZL6M (ORCPT ); Fri, 26 Jan 2018 06:58:12 -0500 Date: Fri, 26 Jan 2018 12:58:00 +0100 From: Borislav Petkov To: Petr Oros Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] x86/microcode/intel: print previous microcode revision during early update Message-ID: <20180126115800.bvqrzik2f3hmmiah@pd.tnic> References: <20180126103451.16863-1-poros@redhat.com> <20180126104109.slxxoq4vkqytqjxd@pd.tnic> <1516967135.2801.1.camel@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1516967135.2801.1.camel@redhat.com> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 26, 2018 at 12:45:35PM +0100, Petr Oros wrote: > 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. Dmesg tells you if the update was applied or not. And if you really wanna know the old microcode revision, you can boot with "dis_ucode_ldr" and do "grep microcode /proc/cpuinfo". -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.