From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BB46DC43331 for ; Thu, 5 Sep 2019 19:50:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1A8B0206BB for ; Thu, 5 Sep 2019 19:50:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alien8.de header.i=@alien8.de header.b="LqwDLrXK" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391467AbfIETuE (ORCPT ); Thu, 5 Sep 2019 15:50:04 -0400 Received: from mail.skyhub.de ([5.9.137.197]:41570 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2391443AbfIETuB (ORCPT ); Thu, 5 Sep 2019 15:50:01 -0400 Received: from zn.tnic (p200300EC2F0A5F00A978ACDBA8294141.dip0.t-ipconnect.de [IPv6:2003:ec:2f0a:5f00:a978:acdb:a829:4141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id A9CFA1EC09A0; Thu, 5 Sep 2019 21:49:55 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1567712996; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=JrDJwXq+Cc2XOF34AEK9Cfp0HAJlcgYu1a0X2xDSA8I=; b=LqwDLrXKMLTBUf/kDKzv7D9YSLhN9Q8yGg5bdChWlIokqKKpAVBEDk+G4N3hXvKxErFMzG WZ2YK5f/Hg5tjz6tYpo6bUol+Pes9HGzT52cX6D9ghfzdi6TXhuXk41heGbC8DQYTgKj2k Gfr3Sv84SlweMVNnkr9TtBCri6zypxQ= Date: Thu, 5 Sep 2019 21:49:50 +0200 From: Borislav Petkov To: "Raj, Ashok" Cc: Boris Ostrovsky , Mihai Carabas , "H. Peter Anvin" , Ingo Molnar , Jon Grimm , kanth.ghatraju@oracle.com, konrad.wilk@oracle.com, patrick.colp@oracle.com, Thomas Gleixner , Tom Lendacky , x86-ml , linux-kernel@vger.kernel.org Subject: Re: [PATCH] x86/microcode: Add an option to reload microcode even if revision is unchanged Message-ID: <20190905194950.GH19246@zn.tnic> References: <1567056803-6640-1-git-send-email-ashok.raj@intel.com> <20190829060942.GA1312@zn.tnic> <20190829130213.GA23510@araj-mobl1.jf.intel.com> <20190903164630.GF11641@zn.tnic> <41cee473-321c-2758-032a-ccf0f01359dc@oracle.com> <20190905002132.GA26568@otc-nc-03> <20190905072029.GB19246@zn.tnic> <20190905194044.GA3663@otc-nc-03> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190905194044.GA3663@otc-nc-03> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 05, 2019 at 12:40:44PM -0700, Raj, Ashok wrote: > The original description said to load a new microcode file, the content > could have changed, but revision in the header hasn't increased. How does the hardware even accept a revision which is the same as the one already loaded? -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette