Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp65020ybe; Wed, 4 Sep 2019 15:13:52 -0700 (PDT) X-Google-Smtp-Source: APXvYqypvUewfrdySoKrcc1ZsXBlItv1M2LIGZVRJd1joOz2DiPpWPG8euA8LJkAmU46qOnCq58n X-Received: by 2002:a17:90a:de0f:: with SMTP id m15mr494453pjv.18.1567635232689; Wed, 04 Sep 2019 15:13:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567635232; cv=none; d=google.com; s=arc-20160816; b=0yOSOjRPKPJf4zG6oCAgGQoWmNcUPwIeYuL92z707fxMynZpf+OwGB+MP8jZbqV6a4 q4MkKuUT01famGhLn3dh4iPTbVktgj3GByIbT8puQcqa9iKGw8BDYmF2Luo4GaYkdyr2 bcTiIXH2Aw/ZgyeGFf1P4qLF+jqsEHZiQZ21KwTXDefHIsc1IHyF7Oh/TcxLd0Wyil0e snlxHW/YP3nTXGU7lVJHxfQCihcyBN1cQDs0tRAWt+VFddtX7/1nax1XsFAWmbddKc5y 9WZbBE38X2FEvBkgd3s4RoWh+PoAVPjPpu56FYPlaXraETOTMuFTCoom7Z524qVkZyWu P0Eg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:from:cc:to:subject :content-transfer-encoding:mime-version:references:in-reply-to :user-agent:date:dkim-signature; bh=2BxOUiVFKBguy8GJUpMo0HYnSyrRDVPrj1TOB9eE+5U=; b=B6KCOhW7/LzJk9XKBO7LRElMSoFlUnxfO7s0cUNrZk4y5hmkCS+MPoaD8RJd65zcLV 3ABJ2YWtUHldIYwuz0Ogk/fii9U/bigTa34tUY9+sgw03NHRh9HPp/a/VuXoqX1Wxws0 J8WmQmXACSDAVBsoAmNKPr66DDir9HQh6L9K9pT1GXdGb2EksruF5cdOyuTUYVJraOIS il2QbyiDMOtprzWQGvGJqhytLTfEtkpmhT6XTbEQ5c1e7VBnwKVCnGE+vZnLu+BWQ1RN jvJAr6tMaE9wyOx0/nmui+yZnxnt8obdCVeC6cKYl9T1/NQH1ATAJRTFNVozAoIZz1Ci ZCzA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@alien8.de header.s=dkim header.b=ehzHlgOl; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alien8.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y12si40844pfg.260.2019.09.04.15.13.30; Wed, 04 Sep 2019 15:13:52 -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; dkim=fail header.i=@alien8.de header.s=dkim header.b=ehzHlgOl; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alien8.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728717AbfIDWMd (ORCPT + 99 others); Wed, 4 Sep 2019 18:12:33 -0400 Received: from mail.skyhub.de ([5.9.137.197]:47490 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727125AbfIDWMd (ORCPT ); Wed, 4 Sep 2019 18:12:33 -0400 Received: from [10.161.240.246] (unknown [46.114.32.246]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 390121EC0A91; Thu, 5 Sep 2019 00:12:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1567635152; 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:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=2BxOUiVFKBguy8GJUpMo0HYnSyrRDVPrj1TOB9eE+5U=; b=ehzHlgOlVn+qrPzzS4Sb59NWJXXd80ZgghcMes/MhXG5CknE2QbijAAJKEK0H6SHgTYC9s Pa35ATuKJYpiBtByl10zMD4JczRljKGPcILLGmj4yq0NMNG1BdPULFdTvY6i5hJXKyK9hP 4y0tA7cyJlBEpE5vfzRoHkbIPU+B+GQ= Date: Thu, 05 Sep 2019 00:12:29 +0200 User-Agent: K-9 Mail for Android In-Reply-To: <41cee473-321c-2758-032a-ccf0f01359dc@oracle.com> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PATCH] x86/microcode: Add an option to reload microcode even if revision is unchanged To: Boris Ostrovsky , "Raj, Ashok" CC: 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 From: Boris Petkov Message-ID: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On September 5, 2019 12:06:54 AM GMT+02:00, Boris Ostrovsky wrote: >Why do we need to taint kernel here? We are not making any changes=2E Because this is not a normal operation we want users to do=2E This is only= for testing microcode quicker=2E >This won't allow people to load from new microcode blob which I thought >was one of the objectives behind this new feature=2E You load a new blob the usual way: echo 1 > =2E=2E=2E This is the "unusual" way where you reload an already loaded revision only= =2E --=20 Sent from a small device: formatting sux and brevity is inevitable=2E