| /linux-6.3-rc2/Documentation/x86/ |
| A D | microcode.rst | 18 Early load microcode
32 The microcode files in cpio name space are:
35 kernel/x86/microcode/GenuineIntel.bin
37 kernel/x86/microcode/AuthenticAMD.bin
40 scans the microcode file in the initrd. If microcode matching the
63 DSTDIR=kernel/x86/microcode
103 The loading mechanism looks for microcode blobs in
117 The microcode engine which receives the microcode update is shared
122 Since the microcode can "simulate" MSRs too, while the microcode update
188 Is the microcode suitable for late loading?
[all …]
|
| A D | mds.rst | 77 instruction in combination with a microcode update. The microcode clears
87 executed on a CPU without the microcode update there is no side effect
102 the microcode updated, but the hypervisor does not (yet) expose the
124 scenarios where the host has the updated microcode but the
191 functionality in microcode. Aside of that the IO-Port mechanism is a
193 not affected or do not receive microcode updates anymore.
|
| A D | index.rst | 32 microcode
|
| A D | tsx_async_abort.rst | 26 microcode update which can be used to disable TSX. In addition, it
48 scenarios where the host has the updated microcode but the
|
| /linux-6.3-rc2/Documentation/powerpc/ |
| A D | qe_firmware.rst | 45 integers that compose the actual QE microcode.
50 1) describes the microcode's purpose
51 2) describes how and where to upload the microcode
62 disables the microcode) must be performed first.
76 in the microcode.
178 the microcode.
211 the microcode to the SOC itself. Normally, the microcode loader should
241 'microcode' (type: struct qe_microcode):
246 identifies this particular microcode.
257 microcode.
[all …]
|
| /linux-6.3-rc2/arch/x86/kernel/cpu/microcode/ |
| A D | Makefile | 2 microcode-y := core.o
3 obj-$(CONFIG_MICROCODE) += microcode.o
4 microcode-$(CONFIG_MICROCODE_INTEL) += intel.o
5 microcode-$(CONFIG_MICROCODE_AMD) += amd.o
|
| A D | intel.c | 556 csig->rev = c->microcode; in collect_cpu_info()
624 c->microcode = rev; in apply_microcode_intel()
628 boot_cpu_data.microcode = rev; in apply_microcode_intel()
731 c->microcode < 0x0b000021) { in is_blacklisted()
732 …rr_once("Erratum BDF90: late loading with revision < 0x0b000021 (0x%x) disabled.\n", c->microcode); in is_blacklisted()
|
| A D | core.c | 440 int old = boot_cpu_data.microcode, ret; in microcode_reload_late()
458 old, boot_cpu_data.microcode); in microcode_reload_late()
462 boot_cpu_data.microcode); in microcode_reload_late()
|
| A D | amd.c | 670 csig->rev = c->microcode; in collect_cpu_info_amd()
726 c->microcode = rev; in apply_microcode_amd()
730 boot_cpu_data.microcode = rev; in apply_microcode_amd()
879 if (c->microcode >= p->patch_id) in load_microcode_amd()
|
| /linux-6.3-rc2/Documentation/power/ |
| A D | suspend-and-cpuhotplug.rst | 176 There are some interesting situations involving CPU hotplug and microcode
179 [Please bear in mind that the kernel requests the microcode images from
187 to apply the same microcode revision to each of the CPUs.
190 and thereby in applying the correct microcode revision to it.
208 (which is sent by the CPU hotplug code), the microcode update driver's
210 microcode image for that CPU.
213 doesn't have the microcode image, it does the CPU type/model discovery
221 have a valid microcode image. This ensures that the CPU type/model
226 d. Handling microcode update during suspend/hibernate:
246 the existing copy of microcode image in the kernel is not freed up.
[all …]
|
| /linux-6.3-rc2/Documentation/admin-guide/hw-vuln/ |
| A D | tsx_async_abort.rst | 100 * - 'Vulnerable: Clear CPU buffers attempted, no microcode'
114 If the processor is vulnerable, but the availability of the microcode-based
120 microcode update applied, but the hypervisor is not yet updated to expose the
121 CPUID to the guest. If the host has updated microcode the protection takes
132 required. If a CPU is affected and the microcode is available, then the kernel
142 Affected systems where the host has TAA microcode and TAA is mitigated by
146 In all other cases, if the host either does not have the TAA microcode or
192 and which get the new IA32_TSX_CTRL MSR through a microcode
219 tsx=off tsx_async_abort=full TSX might be disabled if microcode
238 0 0 0 Vulnerable (needs microcode)
[all …]
|
| A D | special-register-buffer-data-sampling.rst | 64 Intel will release microcode updates that modify the RDRAND, RDSEED, and
86 The microcode updates provide an opt-out mechanism (RNGDS_MITG_DIS) to disable
100 9]==1. This MSR is introduced through the microcode update.
132 Vulnerable: No microcode Processor vulnerable and microcode is missing
147 This new microcode serializes processor access during execution of RDRAND,
|
| A D | mds.rst | 104 * - 'Vulnerable: Clear CPU buffers attempted, no microcode'
105 - The processor is vulnerable but microcode is not updated.
127 If the processor is vulnerable, but the availability of the microcode based
133 microcode update applied, but the hypervisor is not yet updated to expose
134 the CPUID to the guest. If the host has updated microcode the protection
143 The kernel detects the affected CPUs and the presence of the microcode
146 If a CPU is affected and the microcode is available, then the kernel
176 If the L1D flush mitigation is enabled and up to date microcode is
|
| A D | processor_mmio_stale_data.rst | 14 vulnerabilities includes a combination of microcode update and software
115 Newer processors and microcode update on existing affected processors added new
157 combination with a microcode update. The microcode clears the affected CPU
227 * - 'Vulnerable: Clear CPU buffers attempted, no microcode'
228 - The processor is vulnerable, but microcode is not updated. The
|
| /linux-6.3-rc2/drivers/net/wireless/intel/iwlegacy/ |
| A D | Kconfig | 22 In order to use this driver, you will need a microcode (uCode)
23 image for it. You can obtain the microcode from:
27 The microcode is typically installed in /lib/firmware. You can
49 In order to use this driver, you will need a microcode (uCode)
50 image for it. You can obtain the microcode from:
54 The microcode is typically installed in /lib/firmware. You can
|
| /linux-6.3-rc2/drivers/crypto/cavium/cpt/ |
| A D | cptpf.h | 22 struct microcode { struct
53 struct microcode mcode[CPT_MAX_CORE_GROUPS]; argument
|
| A D | cptpf_main.c | 122 static int cpt_load_microcode(struct cpt_device *cpt, struct microcode *mcode) in cpt_load_microcode()
160 static int do_cpt_init(struct cpt_device *cpt, struct microcode *mcode) in do_cpt_init()
257 struct microcode *mcode; in cpt_ucode_load_fw()
417 struct microcode *mcode = &cpt->mcode[grp]; in cpt_unload_microcode()
|
| /linux-6.3-rc2/arch/x86/kernel/cpu/ |
| A D | proc.c | 83 if (c->microcode) in show_cpuinfo()
84 seq_printf(m, "microcode\t: 0x%x\n", c->microcode); in show_cpuinfo()
|
| A D | match.c | 86 if (!res || res->x86_microcode_rev > boot_cpu_data.microcode) in x86_cpu_has_min_microcode_rev()
|
| A D | intel.c | 139 u32 microcode; member
182 return (c->microcode <= spectre_bad_microcodes[i].microcode); in bad_spectre_microcode()
379 c->microcode = intel_get_microcode_revision(); in early_init_intel()
406 c->microcode < 0x20e) { in early_init_intel()
|
| A D | Makefile | 48 obj-$(CONFIG_MICROCODE) += microcode/
|
| /linux-6.3-rc2/arch/x86/include/uapi/asm/ |
| A D | mce.h | 37 __u32 microcode; /* Microcode revision */ member
|
| /linux-6.3-rc2/drivers/soc/fsl/qe/ |
| A D | qe.c | 483 calc_size = struct_size(firmware, microcode, firmware->count); in qe_upload_firmware()
492 be32_to_cpu(firmware->microcode[i].count); in qe_upload_firmware()
534 const struct qe_microcode *ucode = &firmware->microcode[i]; in qe_upload_firmware()
|
| /linux-6.3-rc2/Documentation/networking/devlink/ |
| A D | sfc.rst | 37 - Datapath software/microcode/firmware version.
|
| /linux-6.3-rc2/Documentation/ |
| A D | Changes | 275 Intel IA32 microcode
278 A driver has been added to allow updating of Intel IA32 microcode,
283 mknod /dev/cpu/microcode c 10 184
284 chmod 0644 /dev/cpu/microcode
495 Intel P6 microcode
|