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=-13.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham 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 99269C433DF for ; Mon, 1 Jun 2020 17:19:22 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 6E208206E2 for ; Mon, 1 Jun 2020 17:19:22 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6E208206E2 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=citrix.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1jfo5b-00063Q-Rj; Mon, 01 Jun 2020 17:19:07 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1jfo5a-00063L-SE for xen-devel@lists.xenproject.org; Mon, 01 Jun 2020 17:19:06 +0000 X-Inumbo-ID: fea966b2-a42b-11ea-9947-bc764e2007e4 Received: from ppsw-31.csi.cam.ac.uk (unknown [131.111.8.131]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id fea966b2-a42b-11ea-9947-bc764e2007e4; Mon, 01 Jun 2020 17:19:05 +0000 (UTC) X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus Received: from 88-109-182-220.dynamic.dsl.as9105.com ([88.109.182.220]:54576 helo=[192.168.1.219]) by ppsw-31.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:465) with esmtpsa (PLAIN:amc96) (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) id 1jfo5R-000aMz-Kp (Exim 4.92.3) (return-path ); Mon, 01 Jun 2020 18:18:57 +0100 Subject: Re: [PATCH for-4.14] docs/ucode: Extend runtime microcode loading documentation To: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= References: <20200601134025.24142-1-andrew.cooper3@citrix.com> <20200601165105.GU1195@Air-de-Roger> From: Andrew Cooper Message-ID: <46ae5234-5f0f-e963-7857-520743e047f9@citrix.com> Date: Mon, 1 Jun 2020 18:18:56 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20200601165105.GU1195@Air-de-Roger> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-GB X-BeenThere: xen-devel@lists.xenproject.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Cc: Stefano Stabellini , Julien Grall , Wei Liu , Konrad Rzeszutek Wilk , George Dunlap , Paul Durrant , Jan Beulich , Ian Jackson , Xen-devel Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" On 01/06/2020 17:51, Roger Pau Monné wrote: > > On Mon, Jun 01, 2020 at 02:40:25PM +0100, Andrew Cooper wrote: >> Extend the disclaimer about runtime loading. While we've done our best to >> make the mechaism reliable, the safety of late loading does ultimately depend >> on the contents of the blobs. >> >> Extend the xen-ucode portion with examples of how to use it. >> >> Signed-off-by: Andrew Cooper > Reviewed-by: Roger Pau Monné Thanks, > >> --- >> CC: George Dunlap >> CC: Ian Jackson >> CC: Jan Beulich >> CC: Konrad Rzeszutek Wilk >> CC: Stefano Stabellini >> CC: Wei Liu >> CC: Julien Grall >> CC: Paul Durrant >> --- >> docs/admin-guide/microcode-loading.rst | 22 +++++++++++++++++++--- >> 1 file changed, 19 insertions(+), 3 deletions(-) >> >> diff --git a/docs/admin-guide/microcode-loading.rst b/docs/admin-guide/microcode-loading.rst >> index 5f0f661a2e..8cd5d0351b 100644 >> --- a/docs/admin-guide/microcode-loading.rst >> +++ b/docs/admin-guide/microcode-loading.rst >> @@ -104,8 +104,8 @@ modules to find any CPIO archives, and search the archive for the applicable >> file. Xen will stop searching at the first match. >> >> >> -Run time microcode loading >> --------------------------- >> +Runtime microcode loading >> +------------------------- >> >> .. warning:: >> >> @@ -113,7 +113,23 @@ Run time microcode loading >> or at boot time. Not all microcode updates (or parts thereof) can be >> applied at runtime. >> >> -The ``xen-ucode`` utility can be used to initiate a runtime microcode load. >> + Given the proprietry nature of microcode, we are unable to make any claim >> + that a runtime microcode is risk-free. Any runtime microcode loading needs >> + adequate testing on a dev instance before being rolled out to production >> + systems. >> + >> +The ``xen-ucode`` utility can be used to initiate a runtime microcode load:: >> + >> + [root@host ~]# xen-ucode >> + xen-ucode: Xen microcode updating tool >> + Usage: xen-ucode >> + [root@host ~]# >> + >> +e.g. With a Linux dom0 on a Haswell system:: >> + >> + [root@host ~]# xen-ucode /lib/firmware/intel-ucode/06-3c-03 > Could you expand a bit on the nomenclature used here? > > I assume it's something like -- but might be good > to provide people a hint to know how to find the appropriate blob for > their system if possible. It is $FAMILY-$MODEL-$STEPPING.  Currently only a single version of each microcode is installed at once by the microcode_ctl package. However, its infeasible to cater to all setup's/situations here.  Within linux, you could clone https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/ or use the slightly older single monolithic microcode.dat. And that is before you start considering non-Intel systems, or other ways of packaging microcode. I'm open to suggestions for how to make this clearer, but we definitely can't do an exhaustive list of places you might find microcode. ~Andrew