From nobody Mon May 6 08:47:30 2024 Delivered-To: importer@patchew.org Authentication-Results: mx.zohomail.com; dkim=fail; spf=none (zoho.com: 192.237.175.120 is neither permitted nor denied by domain of lists.xenproject.org) smtp.mailfrom=xen-devel-bounces@lists.xenproject.org; dmarc=fail(p=none dis=none) header.from=citrix.com ARC-Seal: i=1; a=rsa-sha256; t=1570904420; cv=none; d=zoho.com; s=zohoarc; b=PDNVVegE6BvTTzdUZ9xfDXZ51EhZQ+11nmw8P8PctLe+/NRAiT2YAQnvn1e/9UqhJN2ZSwOpZ6ljM47FpHZXXgmCMhxYzyB7R46msUWUqUsscBEi2z5AMd1tL1viDILoTziZayw49AnSdnCytY89QSOnqvGQckivD6VM2+cHgvY= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zoho.com; s=zohoarc; t=1570904420; h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:List-Subscribe:List-Post:List-Id:List-Help:List-Unsubscribe:MIME-Version:Message-ID:Sender:Subject:To; bh=Hx8BzthIZBqmLXq3vE7vywqx8U4qqM79uYIQaguAvdY=; b=EnKGEgm4nVhnioXptXeaPJIhvf/U2SytXXjN6C9sap3R9VrCLTU0YsxSeLF0bswEBJp8FN0N137bnH0A/Mxu7w46+DL8xcZmsADgEcsmBpEyx+riZZrjePW5VjmqYTo/Z9vc8MyKR0TCUP4I9RcQdbXTGxMybskWCIFwLgMr8s0= ARC-Authentication-Results: i=1; mx.zoho.com; dkim=fail; spf=none (zoho.com: 192.237.175.120 is neither permitted nor denied by domain of lists.xenproject.org) smtp.mailfrom=xen-devel-bounces@lists.xenproject.org; dmarc=fail header.from= (p=none dis=none) header.from= Return-Path: Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) by mx.zohomail.com with SMTPS id 1570904420250341.07649229889137; Sat, 12 Oct 2019 11:20:20 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1iJLyr-0002VH-Sr; Sat, 12 Oct 2019 18:19:05 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1iJLyr-0002VC-1y for xen-devel@lists.xenproject.org; Sat, 12 Oct 2019 18:19:05 +0000 Received: from esa1.hc3370-68.iphmx.com (unknown [216.71.145.142]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id c50b072e-ed1c-11e9-bbab-bc764e2007e4; Sat, 12 Oct 2019 18:19:03 +0000 (UTC) X-Inumbo-ID: c50b072e-ed1c-11e9-bbab-bc764e2007e4 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=citrix.com; s=securemail; t=1570904344; h=from:to:cc:subject:date:message-id:mime-version; bh=lvW8o85sda6RCA9ctUQgVi7PoEtJO0TQjHgTMs6quKw=; b=XVm6hhOifC9pW9d3lABQF5kQIk8S+Pj6gOqxkJQWGhRDVBcHtUuC9Ind IO8a02tOg7fNrYBSLcvV2A8fg2+CQBWDwXzVjGZmHcA+RdR1bqUsvcDmj OwKdi9cVmCYtPOJg4Kyfo6y9/djBggmqXWkTxzqwvsR0FZVQwQEce4und 4=; Authentication-Results: esa1.hc3370-68.iphmx.com; dkim=none (message not signed) header.i=none; spf=None smtp.pra=andrew.cooper3@citrix.com; spf=Pass smtp.mailfrom=Andrew.Cooper3@citrix.com; spf=None smtp.helo=postmaster@mail.citrix.com Received-SPF: none (zoho.com: 192.237.175.120 is neither permitted nor denied by domain of lists.xenproject.org) client-ip=192.237.175.120; envelope-from=xen-devel-bounces@lists.xenproject.org; helo=lists.xenproject.org; Received-SPF: None (esa1.hc3370-68.iphmx.com: no sender authenticity information available from domain of andrew.cooper3@citrix.com) identity=pra; client-ip=162.221.158.21; receiver=esa1.hc3370-68.iphmx.com; envelope-from="Andrew.Cooper3@citrix.com"; x-sender="andrew.cooper3@citrix.com"; x-conformance=sidf_compatible Received-SPF: Pass (esa1.hc3370-68.iphmx.com: domain of Andrew.Cooper3@citrix.com designates 162.221.158.21 as permitted sender) identity=mailfrom; client-ip=162.221.158.21; receiver=esa1.hc3370-68.iphmx.com; envelope-from="Andrew.Cooper3@citrix.com"; x-sender="Andrew.Cooper3@citrix.com"; x-conformance=sidf_compatible; x-record-type="v=spf1"; x-record-text="v=spf1 ip4:209.167.231.154 ip4:178.63.86.133 ip4:195.66.111.40/30 ip4:85.115.9.32/28 ip4:199.102.83.4 ip4:192.28.146.160 ip4:192.28.146.107 ip4:216.52.6.88 ip4:216.52.6.188 ip4:162.221.158.21 ip4:162.221.156.83 ip4:168.245.78.127 ~all" Received-SPF: None (esa1.hc3370-68.iphmx.com: no sender authenticity information available from domain of postmaster@mail.citrix.com) identity=helo; client-ip=162.221.158.21; receiver=esa1.hc3370-68.iphmx.com; envelope-from="Andrew.Cooper3@citrix.com"; x-sender="postmaster@mail.citrix.com"; x-conformance=sidf_compatible IronPort-SDR: pV8DUQ2vnYzohalSNo4X04cWxuV1vSsPNRGLSfaBfiHdysUf5nYsyizjsqhPHKP7tkzX+cmZeh AYYP+BSdB23IZ2383TP/yRufODb7O/6DFNle/7CKdzWYwgaFKjXeu0pttHbxsG3OIYZazIaz/b 3XmEOsI/4skr9M6tuIlu63JeMH2CIWbLi6SnL8CeNOw5rv+gMZRpJVI1g7n8Eqiz4I3T/kYTSc RvDEuINGjJ3nM2GST5b15aSdJleEhZfZ17hOdz0GL+Gbq0ks31LLkF4nCoNeYu7nc9bBG4JpSv sOA= X-SBRS: 2.7 X-MesageID: 6887492 X-Ironport-Server: esa1.hc3370-68.iphmx.com X-Remote-IP: 162.221.158.21 X-Policy: $RELAYED X-IronPort-AV: E=Sophos;i="5.67,288,1566878400"; d="scan'208";a="6887492" From: Andrew Cooper To: Xen-devel Date: Sat, 12 Oct 2019 19:18:59 +0100 Message-ID: <20191012181859.11110-1-andrew.cooper3@citrix.com> X-Mailer: git-send-email 2.11.0 MIME-Version: 1.0 Subject: [Xen-devel] [PATCH for-4.13] docs: Extend with details about runtime microcode loading X-BeenThere: xen-devel@lists.xenproject.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Cc: Juergen Gross , Lars Kurth , Stefano Stabellini , Julien Grall , Wei Liu , Konrad Rzeszutek Wilk , George Dunlap , Andrew Cooper , Tim Deegan , Jan Beulich , Ian Jackson Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" X-ZohoMail-DKIM: fail (Header signature does not verify) The xen-ucode utility is new with the late loading improvements in 4.13. Update the documentation suitably. Signed-off-by: Andrew Cooper Acked-by: Jan Beulich --- CC: George Dunlap CC: Ian Jackson CC: Jan Beulich CC: Konrad Rzeszutek Wilk CC: Stefano Stabellini CC: Tim Deegan CC: Wei Liu CC: Julien Grall CC: Juergen Gross CC: Lars Kurth For 4.13. This is documentation concerning new work. The additions for choosing the application policy, and logic to rescan CPUID/MSRs and start using the new functionatly will have to wait for 4.14 = at this point. If anyone is curious about the wording of the warning, it should come as no surprise that an individual blob of microcode might contain more than one thing. On anything semi-modern system, there is Core microcode (the pipeli= ne itself), and Uncore microcode (the "rest" of the integrated functionality on the chip), as well as other ancillary pieces. --- docs/admin-guide/microcode-loading.rst | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/docs/admin-guide/microcode-loading.rst b/docs/admin-guide/micr= ocode-loading.rst index 8265b917a9..e83cadd2c2 100644 --- a/docs/admin-guide/microcode-loading.rst +++ b/docs/admin-guide/microcode-loading.rst @@ -103,3 +103,32 @@ which contains contains one of these two files:: The ``ucode=3Dscan`` command line option will cause Xen to search through = all modules to find any CPIO archives, and search the archive for the applicab= le file. Xen will stop searching at the first match. + + +Run time microcode loading +-------------------------- + +.. warning:: + + If at all possible, microcode updates should be done by firmware update= s, + 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. +It will pass the blob to Xen, which will check to see whether the blob is +correct for the processor, and newer than the running microcode. + +If these checks pass, the entire system will be rendezvoused and an update +will be initiated on all CPUs in parallel. As with boot time loading, +diagnostics will be put out onto the console:: + + [root@host ~]# xl dmesg | grep microcode + (XEN) microcode: CPU0 updated from revision 0x1a to 0x25, date =3D 2018-= 04-02 + (XEN) microcode: CPU2 updated from revision 0x1a to 0x25, date =3D 2018-= 04-02 + (XEN) microcode: CPU4 updated from revision 0x1a to 0x25, date =3D 2018-= 04-02 + (XEN) microcode: CPU6 updated from revision 0x1a to 0x25, date =3D 2018-= 04-02 + (XEN) 4 cores are to update their microcode + (XEN) microcode: CPU0 updated from revision 0x25 to 0x27, date =3D 2019-= 02-26 + (XEN) microcode: CPU4 updated from revision 0x25 to 0x27, date =3D 2019-= 02-26 + (XEN) microcode: CPU2 updated from revision 0x25 to 0x27, date =3D 2019-= 02-26 + (XEN) microcode: CPU6 updated from revision 0x25 to 0x27, date =3D 2019-= 02-26 --=20 2.11.0 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel