/openbmc/linux/Documentation/admin-guide/hw-vuln/ |
H A D | l1tf.rst | 95 multi threading (SMT). The Intel implementation of SMT is called 138 - SMT status: 141 'VMX: SMT vulnerable' SMT is enabled 142 'VMX: SMT disabled' SMT is disabled 205 **Note**, that L1D flush does not prevent the SMT problem because the 218 To address the SMT problem, it is possible to make a guest or a group of 223 If only a single guest or related guests run on sibling SMT threads on 227 Host memory is attackable, when one of the sibling SMT threads runs in 238 scenario. Disabling SMT might be a viable alternative for particular 275 4. SMT control [all …]
|
H A D | mds.rst | 116 'SMT vulnerable' SMT is enabled 117 'SMT mitigated' SMT is enabled and mitigated 118 'SMT disabled' SMT is disabled 119 'SMT Host state unknown' Kernel runs in a VM, Host SMT state unknown 159 If SMT is enabled it also clears the buffers on idle entry when the CPU 164 transition mitigations are sufficient and SMT is not affected. 226 either disabling SMT is not required for full protection. 230 SMT control 235 disable SMT for full protection. These are most of the affected CPUs; the 238 Disabling SMT can have a significant performance impact, but the impact [all …]
|
H A D | l1d_flush.rst | 60 a physical CPU core when SMT is enabled on the system. 63 cores or by disabling SMT. See the relevant chapter in the L1TF mitigation 67 affinity is limited to cores running in non-SMT mode. If a task which 68 requested L1D flushing is scheduled on a SMT-enabled core the kernel sends
|
H A D | cross-thread-rsb.rst | 8 predictions vulnerability. When running in SMT mode and one sibling thread 38 Affected SMT-capable processors support 1T and 2T modes of execution when SMT 47 depending on the SMT mode. For instance, in 2T mode each thread uses a private 51 change. This behavior may result in return targets from one SMT thread being
|
H A D | processor_mmio_stale_data.rst | 202 protected as well. It does not automatically disable SMT. 203 full,nosmt Same as full, with SMT disabled on vulnerable CPUs. This is the 252 'SMT vulnerable' SMT is enabled 253 'SMT disabled' SMT is disabled 254 'SMT Host state unknown' Kernel runs in a VM, Host SMT state unknown
|
H A D | tsx_async_abort.rst | 169 full,nosmt The same as tsx_async_abort=full, with SMT disabled on 171 mitigation. When TSX is disabled, SMT is not disabled because 215 possible on SMT machines. 216 tsx=on tsx_async_abort=full,nosmt As above, cross-thread attacks on SMT
|
H A D | spectre.rst | 126 On systems with simultaneous multi-threading (SMT), attacks are possible 235 multi-threading (SMT) system. 255 target buffer. When SMT is enabled on x86, for a process that has 318 If SMT is used, Spectre variant 2 attacks from an untrusted guest 510 injections on SMT systems (STIBP). In other words, Intel eIBRS enables 583 To mitigate guest-to-guest attacks from sibling thread when SMT is
|
H A D | reg-file-data-sampling.rst | 53 before VMentry. None of the affected cores support SMT, so VERW is not required
|
/openbmc/qemu/tests/qtest/ |
H A D | pnv-xive2-test.c | 18 #define SMT 4 /* some tests will break if less than 4 */ macro 111 for (i = 0; i < SMT; i++) { in reset_pool_threads() 126 if (SMT >= 4) { in reset_hw_threads() 135 for (i = 0; i < SMT; i++) { in reset_hw_threads() 325 SMT, SMT); in test_xive()
|
H A D | pnv-xscom.h | 12 #define SMT 4 /* some tests will break if less than 4 */ macro
|
H A D | pnv-host-i2c-test.c | 422 machine, SMT, SMT); in test_host_i2c()
|
/openbmc/linux/kernel/ |
H A D | Kconfig.preempt | 119 bool "Core Scheduling for SMT" 123 selection across SMT siblings. When enabled -- see 124 prctl(PR_SCHED_CORE) -- task selection ensures that all SMT siblings 129 - mitigation of some (not all) SMT side channels; 130 - limiting SMT interference to improve determinism and/or performance.
|
/openbmc/linux/Documentation/translations/zh_CN/scheduler/ |
H A D | sched-energy.rst | 345 6.6 多线程(SMT) 348 当前实现的EAS是不感知SMT的,因此无法利用多线程硬件节约能量。EAS认为线程是独立的 351 不支持在SMT上使用EAS。
|
H A D | sched-domains.rst | 55 基调度域会管辖CPU层次结构中的第一层。对于超线程(SMT)而言,基调度域将会管辖同一个物理
|
/openbmc/linux/Documentation/networking/device_drivers/fddi/ |
H A D | defza.rst | 39 supports separate enables for LLC and SMT frames, but this driver 55 7. Queueing incoming/outgoing SMT frames in the driver if the SMT
|
H A D | skfp.rst | 144 changed in SMT version v2.82. With this new SMT version, the yellow 150 With versions of SMT prior to v2.82 a ring up was indicated if the 209 - New SMT module included, changing LED functionality
|
/openbmc/linux/Documentation/devicetree/bindings/cpu/ |
H A D | cpu-topology.txt | 18 symmetric multi-threading (SMT) is supported or not. 20 For instance in a system where CPUs support SMT, "cpu" nodes represent all 22 In systems where SMT is not supported "cpu" nodes represent all cores present 138 the cluster. If the system does not support SMT, core 144 A core node must be a leaf node if SMT is not supported. 154 If a core node is not a leaf node (CPUs supporting SMT) a core node's 164 in the core if the system supports SMT. Thread nodes are 405 Example 2 (ARM 32-bit, dual-cluster, 8-cpu system, no SMT):
|
/openbmc/linux/Documentation/arch/x86/ |
H A D | microcode.rst | 118 between the two logical threads in a SMT system. Therefore, when 119 the update is executed on one SMT thread of the core, the sibling 124 can result in unpredictable results if the SMT sibling thread happens to 131 executed by the other SMT sibling, can also result in similar,
|
H A D | mds.rst | 74 thread case (SMT off): Force the CPU to clear the affected buffers. 174 cleared on affected CPUs when SMT is active. This addresses the 178 When SMT is inactive, i.e. either the CPU does not support it or all 189 switched depending on the chosen mitigation mode and the SMT state of
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-devices-system-cpu | 550 Description: Control Symmetric Multi Threading (SMT) 552 active: Tells whether SMT is active (enabled and siblings online) 554 control: Read/write interface to control SMT. Possible 558 "on" SMT is enabled 559 "off" SMT is disabled 560 "<N>" SMT is enabled with N threads per core. 561 "forceoff" SMT is force disabled. Cannot be changed. 562 "notsupported" SMT is not supported by the CPU 563 "notimplemented" SMT runtime toggling is not 568 are rejected. Note that enabling SMT on PowerPC skips
|
/openbmc/linux/Documentation/admin-guide/pm/ |
H A D | intel_epb.rst | 40 example, SMT siblings or cores in one package). For this reason, updating the
|
/openbmc/linux/Documentation/accounting/ |
H A D | taskstats-struct.rst | 36 5) Time accounting for SMT machines 185 5) Time accounting for SMT machines::
|
/openbmc/qemu/qapi/ |
H A D | machine-common.json | 27 # @thread: thread level, which would also be called SMT level or
|
/openbmc/linux/Documentation/userspace-api/ |
H A D | spec_ctrl.rst | 111 (works only when tasks run on non SMT cores)
|
/openbmc/linux/Documentation/admin-guide/media/ |
H A D | cx88-cardlist.rst | 354 - Samsung SMT 7020 DVB-S
|