Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp652166ybe; Thu, 5 Sep 2019 03:54:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqx/HuT0SvtwEUOY2psGl5ZYijQ+nmG0A4LChcTIHOxU4MA3ibl77xr8H8f3Ptv632TOfKnw X-Received: by 2002:a63:1908:: with SMTP id z8mr2470306pgl.433.1567680846982; Thu, 05 Sep 2019 03:54:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567680846; cv=none; d=google.com; s=arc-20160816; b=k/E1ptKkaK/5Gf6xiLRY5PcsjLLkZpmwPH3fzCtjcXw2mUQNvqEiUYp8vHB7DaHfDR Xtz7//Qr2KY7fsO04CX472IPuyhg8/BOniBdcumx8Eb3o72ACtZKPOcdri4Kl1oHEFXL 8Lk5r8ADXfspZfFt9ZbPHeZfEsMUSd0l+gpQN7hlvDjo5r1068GASebf5judKtJlmMJM ZkRPK51+GDlwxFQ455K4m7OQ4igS+ZNntvvy7kDi27ahVePd6GgE3yO+mj9K1lOwlKvE 706Ej2SsGDGRIjOxlOloQKYvBQLS5b9OPFDP5wukENlUOuOsmFoRoW8HgjBsbfdj1Uuh bMgg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=zki752qN2Kso+2aOCOsrcJN5LkLqWsDummR+x+Uv29U=; b=mxmE6HULgjwdqv2n44lTUgFYGHIqkJxxOR9M7RJ9OkLJTvtRqKJI/nCLSoNzeqoa8y WOqCZqHW6Yz7dsHpkJUNXXcKTjZ0KXfb+FO4XmDHVUazT6/ieoWW48O1uZ1fCmqokJ5h WN/wGpoxzpeRVC4oFJnM6sZHZuExmtjoIAiRJNCTkTbMYqkGGJ3OuITZBfnmx5KsVqui z1Qxm2aap0dn7lQ/KLulRLC+hRYT97Pu/xvLR49oUA3Na5gu4PBAdqm4i+Hy5fl/UZ82 B1UqPS14GQwMEpAL/w++ZBuh+CP97xZPQlV84Pp12Xc4XByVnw6N0pq3lskH9z8Q6lrT rdnA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j16si1747182pjz.31.2019.09.05.03.53.51; Thu, 05 Sep 2019 03:54:06 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733138AbfIEKvm (ORCPT + 99 others); Thu, 5 Sep 2019 06:51:42 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:42419 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731476AbfIEKvm (ORCPT ); Thu, 5 Sep 2019 06:51:42 -0400 Received: from p5de0b6c5.dip0.t-ipconnect.de ([93.224.182.197] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1i5pMG-0005iC-Gn; Thu, 05 Sep 2019 12:51:20 +0200 Date: Thu, 5 Sep 2019 12:51:18 +0200 (CEST) From: Thomas Gleixner To: Borislav Petkov cc: "Raj, Ashok" , Boris Ostrovsky , Mihai Carabas , "H. Peter Anvin" , Ingo Molnar , Jon Grimm , kanth.ghatraju@oracle.com, konrad.wilk@oracle.com, patrick.colp@oracle.com, 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 In-Reply-To: <20190905072029.GB19246@zn.tnic> Message-ID: 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> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 5 Sep 2019, Borislav Petkov wrote: > On Wed, Sep 04, 2019 at 05:21:32PM -0700, Raj, Ashok wrote: > > But echo 2 > reload would allow reading a microcode file from > > /lib/firmware/intel-ucode/ even if the revision hasn't changed right? > > > > #echo 1 > reload wouldn't load if the revision on disk is same as what's loaded, > > and we want to permit that with the echo 2 option. > > Then before we continue with this, please specify what the exact > requirements are. Talk to your microcoders or whoever is going to use > this and give the exact use cases which should be supported and describe > them in detail. Plus I have to ask whether this facility makes any sense outside of microcode development. If so, then please explain the use case and give a proper justification why this needs to be in the mainline kernel. Thanks, tglx