Home
last modified time | relevance | path

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

12345678910>>...14

/OK3568_Linux_fs/kernel/Documentation/admin-guide/hw-vuln/
H A Dprocessor_mmio_stale_data.rst9 are not affected. System environments using virtualization where MMIO access is
61 processors affected by FBSDP, this may expose stale data from the fill buffers
67 into client core fill buffers, processors affected by MFBDS can leak data from
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
115 Newer processors and microcode update on existing affected processors added new
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
127 Bit 15 - PSDP_NO - When set, processor is not affected by Primary Stale Data
[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'
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
156 The mitigation for MDS clears the affected CPU buffers on return to user
160 is only affected by MSBDS and not any other MDS variant, because the
163 For CPUs which are only affected by MSBDS the user space, guest and idle
164 transition mitigations are sufficient and SMT is not affected.
174 - CPU is affected by L1TF:
[all …]
H A Dtsx_async_abort.rst19 Whether a processor is affected or not can be read out from the TAA
99 …- The CPU is affected by this vulnerability and the microcode and kernel mitigation are not applie…
106 * - 'Not affected'
107 - The CPU is not affected by this issue.
131 The kernel detects the affected CPUs and the presence of the microcode which is
132 required. If a CPU is affected and the microcode is available, then the kernel
159 off This option disables the TAA mitigation on affected platforms.
161 is affected, the system is vulnerable.
163 full TAA mitigation is enabled. If TSX is enabled, on an affected
165 systems which are MDS-affected and deploy MDS mitigation,
[all …]
H A Dspecial-register-buffer-data-sampling.rst19 be affected.
21 A processor is affected by SRBDS if its Family_Model and stepping is
24 latter class of processors are only affected when Intel TSX is enabled
25 by software using TSX_CTRL_MSR otherwise they are not affected.
117 affected platforms.
129 Not affected Processor not vulnerable
140 affected but with no way to know if host
/OK3568_Linux_fs/external/xserver/xkb/
H A DxkbLEDs.c242 register unsigned i, bit, affected; in XkbUpdateLedAutoState() local
256 affected = maps_to_check; in XkbUpdateLedAutoState()
258 sli->autoState &= ~affected; in XkbUpdateLedAutoState()
259 for (i = 0, bit = 1; (i < XkbNumIndicators) && (affected); i++, bit <<= 1) { in XkbUpdateLedAutoState()
260 if ((affected & bit) == 0) in XkbUpdateLedAutoState()
262 affected &= ~bit; in XkbUpdateLedAutoState()
269 affected = sli->effectiveState ^ oldState; in XkbUpdateLedAutoState()
270 if (affected == 0) in XkbUpdateLedAutoState()
287 changes->indicators.state_changes |= affected; in XkbUpdateLedAutoState()
930 register unsigned i, bit, affected; in XkbApplyLedStateChanges() local
[all …]
/OK3568_Linux_fs/kernel/Documentation/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.
83 VERW can be avoided. If the CPU is not affected by L1TF then VERW needs to
116 off Mitigation is disabled. Either the CPU is not affected or
119 full Mitigation is enabled. CPU is affected and MD_CLEAR is
122 vmwerv Mitigation is enabled. CPU is affected and MD_CLEAR is not
129 If the CPU is affected and mds=off is not supplied on the kernel command
140 on affected CPUs when the mitigation is not disabled on the kernel
158 cleared on affected CPUs when SMT is active. This addresses the
165 The idle clearing is enabled on CPUs which are only affected by MSBDS
[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
/OK3568_Linux_fs/buildroot/package/boost/
H A DConfig.in118 comment "boost-coroutine needs a toolchain not affected by GCC bug 64735"
156 comment "boost-fiber needs a toolchain not affected by GCC bug 64735"
227 comment "boost-locale needs a toolchain not affected by GCC bug 64735"
250 comment "boost-log needs a toolchain not affected by GCC bug 64735"
355 comment "boost-thread needs a toolchain not affected by GCC bug 64735"
374 comment "boost-type_erasure needs a toolchain not affected by GCC bug 64735"
394 comment "boost-wave needs a toolchain not affected by GCC bug 64735"
/OK3568_Linux_fs/kernel/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.
/OK3568_Linux_fs/u-boot/arch/arm/cpu/armv7/
H A Dstart.S223 bge skip_errata_798870 @ skip if not affected rev
225 blt skip_errata_798870 @ skip if not affected rev
238 bgt skip_errata_801819 @ skip if not affected rev
240 blt skip_errata_801819 @ skip if not affected rev
/OK3568_Linux_fs/buildroot/package/ortp/
H A DConfig.in15 comment "ortp needs a toolchain not affected by GCC bug 64735"
/OK3568_Linux_fs/buildroot/package/paho-mqtt-cpp/
H A DConfig.in16 comment "paho-mqtt-cpp needs a toolchain not affected by GCC bug 64735"
/OK3568_Linux_fs/buildroot/package/bctoolbox/
H A DConfig.in18 comment "bctoolbox needs a toolchain not affected by GCC bug 64735"
/OK3568_Linux_fs/buildroot/package/squid/
H A DConfig.in1 comment "squid needs a toolchain w/ C++, gcc >= 4.8 not affected by bug 64735"
/OK3568_Linux_fs/kernel/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
/OK3568_Linux_fs/buildroot/package/stella/
H A DConfig.in21 comment "stella needs a toolchain not affected by GCC bug 64735"
/OK3568_Linux_fs/buildroot/package/git-crypt/
H A DConfig.in20 comment "git-crypt needs a toolchain not affected by GCC bug 64735"
/OK3568_Linux_fs/buildroot/package/belr/
H A DConfig.in18 comment "belr needs a toolchain not affected by GCC bug 64735"
/OK3568_Linux_fs/buildroot/package/log4cplus/
H A DConfig.in20 comment "log4cplus needs a toolchain not affected by GCC bug 64735"
/OK3568_Linux_fs/buildroot/package/belle-sip/
H A DConfig.in21 comment "belle-sip needs a toolchain not affected by GCC bug 64735"
/OK3568_Linux_fs/kernel/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
/OK3568_Linux_fs/u-boot/doc/device-tree-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
/OK3568_Linux_fs/buildroot/package/clang/
H A DConfig.in23 comment "clang needs a toolchain not affected by GCC bug 64735"
/OK3568_Linux_fs/kernel/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,
128 every driver affected by the error.
173 thus, if one device sleeps/schedules, all devices are affected.
190 DMA), and then calls the mmio_enabled() callback on all affected
337 The platform will call the resume() callback on all affected device
/OK3568_Linux_fs/buildroot/package/dillo/
H A D0001-usr-local-include.patch5 in hard errors, failing affected configure tests.

12345678910>>...14