Home
last modified time | relevance | path

Searched refs:affected (Results 1 – 25 of 291) sorted by relevance

12345678910>>...12

/linux-6.15/Documentation/admin-guide/hw-vuln/
H A Dindirect-target-selection.rst28 Below is the list of ITS affected CPUs [#f2]_ [#f3]_:
35 ICELAKE_X 06_6AH Not affected Affected
36 ICELAKE_D 06_6CH Not affected Affected
47 - All affected CPUs enumerate Enhanced IBRS feature.
48 - IBPB isolation is affected on all ITS affected CPUs, and need a microcode
52 host's affected status.
53 - Intel Atom CPUs are not affected by ITS.
108 guests as per the host's affected status.
118 deployed for the affected RET instructions. Retpoline mitigates
149 * - Not affected
[all …]
H A Dreg-file-data-sampling.rst13 Below is the list of affected Intel processors [#f1]_:
36 mitigation strategy to force the CPU to clear the affected buffers before an
39 The microcode clears the affected CPU buffers when the VERW instruction is
45 before VMentry. None of the affected cores support SMT, so VERW is not required
50 Newer processors and microcode update on existing affected processors added new
54 - Bit 27 - RFDS_NO - When set, processor is not affected by RFDS.
55 - Bit 28 - RFDS_CLEAR - When set, processor is affected by RFDS, and has the
56 microcode that clears the affected buffers on VERW execution.
83 * - 'Not affected'
96 …/us/en/developer/topic-technology/software-security-guidance/processors-affected-consolidated-prod…
H A Dprocessor_mmio_stale_data.rst9 are not affected. System environments using virtualization where MMIO access is
79 Not all the CPUs are affected by all the variants. For instance, most
83 Below is the list of affected Intel processors [#f1]_:
108 If a CPU is in the affected processor list, but not affected by a variant, it
122 Bit 13 - SBDR_SSDP_NO - When set, processor is not affected by either the
125 Bit 14 - FBSDP_NO - When set, processor is not affected by the Fill Buffer
131 enumerate MDS_NO (meaning they are affected by MDS) but that do
157 combination with a microcode update. The microcode clears the affected CPU
164 On MDS affected CPUs, the kernel already invokes CPU buffer clear on
177 Same mitigation as MDS when affected by MDS/TAA, otherwise no mitigation
[all …]
H A Dmds.rst23 Whether a processor is affected or not can be read out from the MDS
26 Not all processors are affected by all variants of MDS, but the mitigation
100 * - 'Not affected'
135 The kernel detects the affected CPUs and the presence of the microcode
138 If a CPU is affected and the microcode is available, then the kernel
152 is only affected by MSBDS and not any other MDS variant, because the
156 transition mitigations are sufficient and SMT is not affected.
166 - CPU is affected by L1TF:
178 - CPU is not affected by L1TF:
188 Don't care No Don't care N/A Not affected
[all …]
H A Dtsx_async_abort.rst19 Whether a processor is affected or not can be read out from the TAA
118 * - 'Not affected'
119 - The CPU is not affected by this issue.
124 The kernel detects the affected CPUs and the presence of the microcode which is
125 required. If a CPU is affected and the microcode is available, then the kernel
152 off This option disables the TAA mitigation on affected platforms.
154 is affected, the system is vulnerable.
156 full TAA mitigation is enabled. If TSX is enabled, on an affected
158 systems which are MDS-affected and deploy MDS mitigation,
169 processors that are affected by both TAA and MDS, specifying just
[all …]
H A Dspecial-register-buffer-data-sampling.rst20 be affected.
22 A processor is affected by SRBDS if its Family_Model and stepping is
25 latter class of processors are only affected when Intel TSX is enabled
26 by software using TSX_CTRL_MSR otherwise they are not affected.
118 affected platforms.
130 Not affected Processor not vulnerable
141 affected but with no way to know if host
H A Dgather_data_sampling.rst76 use the microcode mitigation when available or disable AVX on affected systems
89 Not affected Processor not vulnerable.
102 affected but with no way to know if host
H A Dcross-thread-rsb.rst46 In affected processors, the return address predictor (RAP) is partitioned
61 An attack can be mounted on affected processors by performing a series of CALL
/linux-6.15/Documentation/arch/x86/
H A Dmds.rst74 thread case (SMT off): Force the CPU to clear the affected buffers.
78 the affected CPU buffers when the VERW instruction is executed.
119 off Mitigation is disabled. Either the CPU is not affected or
122 full Mitigation is enabled. CPU is affected and MD_CLEAR is
125 vmwerv Mitigation is enabled. CPU is affected and MD_CLEAR is not
132 If the CPU is affected and mds=off is not supplied on the kernel command
143 on affected CPUs when the mitigation is not disabled on the kernel
174 cleared on affected CPUs when SMT is active. This addresses the
181 The idle clearing is enabled on CPUs which are only affected by MSBDS
184 the Load Ports are shared. So on CPUs affected by other variants, the
[all …]
H A Dtsx_async_abort.rst37 off Mitigation is disabled. Either the CPU is not affected or
43 verw Mitigation is enabled. CPU is affected and MD_CLEAR is
46 ucode needed Mitigation is enabled. CPU is affected and MD_CLEAR is not
53 If the CPU is affected and the "tsx_async_abort" kernel command line parameter is
/linux-6.15/arch/m68k/fpsp040/
H A Dx_ovfl.S16 | destination is not affected. For 68881 compatibility, the
174 | CCs are defined to be 'not affected' for the opclass3 instruction.
/linux-6.15/Documentation/hwmon/
H A Daspeed-g6-pwm-tach.rst25 affected by fan signal glitch.
/linux-6.15/Documentation/devicetree/bindings/pinctrl/
H A Dactions,s500-pinctrl.yaml73 List of gpio pin groups affected by the functions specified in
123 List of gpio pin groups affected by the drive-strength property
141 List of gpio pins affected by the bias-pull-* and
/linux-6.15/Documentation/process/
H A Dembargoed-hardware-issues.rst46 While hardware security issues are often handled by the affected silicon
129 description of the problem and a list of any known affected silicon. If
130 your organization builds or distributes the affected hardware, we encourage
131 you to also consider what other hardware could be affected. The disclosing
132 party is responsible for contacting the affected silicon vendors in a
229 To allow the affected silicon vendors to work with their internal teams and
233 Designated representatives of the affected silicon vendors are
236 response team about the handover. The affected silicon vendor must
/linux-6.15/Documentation/ABI/testing/
H A Dsysfs-bus-iio-light-isl2901816 is less affected by the ambient IR noise variation.
H A Dsysfs-devices-state_synced21 at the time the kernel starts are not affected or limited in
/linux-6.15/Documentation/filesystems/
H A Dquota.rst83 - major number of a device with the affected filesystem
85 - minor number of a device with the affected filesystem
/linux-6.15/drivers/soc/hisilicon/
H A DKconfig14 The performance of application may be affected if some HCCS
/linux-6.15/Documentation/devicetree/bindings/reset/
H A Dreset.txt23 the DT node of each affected HW block, since if activated, an unrelated block
26 children of the bus are affected by the reset signal, or an individual HW
/linux-6.15/drivers/parisc/
H A DREADME.dino11 ** not affected."
/linux-6.15/Documentation/gpu/
H A Dautomated_testing.rst71 bug to the author of the affected driver or the relevant GitLab issue. The entry
73 affected, the IGT version used for tests, and an approximation of the failure rate.
125 affected by the change.
/linux-6.15/Documentation/PCI/
H A Dpci-error-recovery.rst18 pSeries boxes. A typical action taken is to disconnect the affected device,
22 offered, so that the affected PCI device(s) are reset and put back
24 between the affected device drivers and the PCI controller chip.
31 is reported as soon as possible to all affected device drivers,
129 every driver affected by the error.
174 thus, if one device sleeps/schedules, all devices are affected.
191 DMA), and then calls the mmio_enabled() callback on all affected
338 The platform will call the resume() callback on all affected device
/linux-6.15/arch/arm64/
H A DKconfig488 the kernel if an affected CPU is detected.
510 the kernel if an affected CPU is detected.
533 only patch the kernel if an affected CPU is detected.
555 the kernel if an affected CPU is detected.
573 the kernel if an affected CPU is detected.
593 the kernel if an affected CPU is detected.
630 the kernel if an affected CPU is detected.
657 of hardware DBM locally on the affected cores. CPUs not affected by
727 Under very rare circumstances, affected Cortex-A55 CPUs
817 is to not enable the feature on affected CPUs.
[all …]
/linux-6.15/arch/m68k/
H A DKconfig.debug17 PROM console functionality on Sun 3x is not affected by this option.
/linux-6.15/Documentation/devicetree/bindings/net/
H A Dethernet-phy-package.yaml14 and each Ethernet PHY is affected by the global configuration

12345678910>>...12