Lines Matching refs:microcode
12 firmware update is the preferred way of obtaining updated microcode. However,
14 loading microcode itself.
16 Distros typically package microcode updates for users, and may provide hooks
17 to cause microcode to be automatically loaded at boot time. Consult your dom0
18 distro guidance for microcode loading.
27 Boot time microcode loading
30 Where possible, microcode should be loaded at boot time. This allows the CPU
34 Xen will report during boot if it performed a microcode update::
36 [root@host ~]# xl dmesg | grep microcode
37 (XEN) microcode: CPU0 updated from revision 0x1a to 0x25, date = 2018-04-02
38 (XEN) microcode: CPU2 updated from revision 0x1a to 0x25, date = 2018-04-02
39 (XEN) microcode: CPU4 updated from revision 0x1a to 0x25, date = 2018-04-02
40 (XEN) microcode: CPU6 updated from revision 0x1a to 0x25, date = 2018-04-02
42 The exact details printed are system and microcode specific. After boot, the
43 current microcode version can obtained from with dom0::
52 microcode : 0x25
58 Loading microcode from a single file
61 Xen handles microcode blobs in the binary form shipped by vendors, which is
82 identify which multiboot module contains the microcode, including negative
85 * For EFI boots, there isn't really a concept of modules. A microcode file
90 Loading microcode from a Linux initrd
96 Xen is compatible with the Linux initrd microcode protocol. The initrd is
100 kernel/x86/microcode/GenuineIntel.bin
101 kernel/x86/microcode/AuthenticAMD.bin
108 Runtime microcode loading
113 If at all possible, microcode updates should be done by firmware updates,
114 or at boot time. Not all microcode updates (or parts thereof) can be
117 Given the proprietary nature of microcode, we are unable to make any claim
118 that runtime microcode loading is risk-free. Any runtime microcode loading
122 The ``xen-ucode`` utility can be used to initiate a runtime microcode load::
125 xen-ucode: Xen microcode updating tool
126 Usage: xen-ucode <microcode blob>
129 The details of microcode blobs (if even packaged to begin with) are specific
137 correct for the processor, and newer than the running microcode.
143 [root@host ~]# xl dmesg | grep microcode
144 (XEN) microcode: CPU0 updated from revision 0x1a to 0x25, date = 2018-04-02
145 (XEN) microcode: CPU2 updated from revision 0x1a to 0x25, date = 2018-04-02
146 (XEN) microcode: CPU4 updated from revision 0x1a to 0x25, date = 2018-04-02
147 (XEN) microcode: CPU6 updated from revision 0x1a to 0x25, date = 2018-04-02
148 (XEN) 4 cores are to update their microcode
149 (XEN) microcode: CPU0 updated from revision 0x25 to 0x27, date = 2019-02-26
150 (XEN) microcode: CPU4 updated from revision 0x25 to 0x27, date = 2019-02-26
151 (XEN) microcode: CPU2 updated from revision 0x25 to 0x27, date = 2019-02-26
152 (XEN) microcode: CPU6 updated from revision 0x25 to 0x27, date = 2019-02-26