| /Linux-v5.4/Documentation/admin-guide/hw-vuln/ |
| D | spectre.rst | 7 and speculative execution on modern CPUs to read memory, possibly
18 use branch prediction and speculative execution.
53 CPUs use speculative operations to improve performance. That may leave
56 influence the speculative execution paths, and then use the side effects
57 of the speculative execution in the CPUs' caches and buffers to infer
58 privileged data touched during the speculative execution.
60 Spectre variant 1 attacks take advantage of speculative execution of
61 conditional branches, while Spectre variant 2 attacks use speculative
70 of speculative execution that bypasses conditional branch instructions
74 done speculatively before validation checks resolve. Such speculative
[all …]
|
| D | tsx_async_abort.rst | 6 TAA is a hardware vulnerability that allows unprivileged speculative access to
29 microprocessors utilizing speculative execution may
|
| D | mds.rst | 5 unprivileged speculative access to data which is available in various CPU
54 may be able to forward this speculative data to a disclosure gadget which
|
| D | l1tf.rst | 5 speculative access to data which is available in the Level 1 Data Cache
48 then speculative execution ignores the invalid PTE and loads the referenced
52 While this is a purely speculative mechanism and the instruction will raise
54 data and making it available to other speculative instructions opens up the
|
| /Linux-v5.4/arch/alpha/lib/ |
| D | ev67-strchr.S | 59 cttz t0, a2 # U0 : speculative (in case we get a match)
76 cttz t3, a2 # U0 : speculative (in case we get a match)
|
| D | ev6-memset.S | 166 addq $5, 128, $4 # E : speculative target of next wh64
344 addq $5, 128, $4 # E : speculative target of next wh64
532 addq $5, 128, $4 # E : speculative target of next wh64
|
| /Linux-v5.4/drivers/staging/most/Documentation/ABI/ |
| D | configfs-most.txt | 49 creation of the link. In case of speculative
93 creation of the link. In case of speculative
137 creation of the link. In case of speculative
191 creation of the link. In case of speculative
|
| /Linux-v5.4/Documentation/ |
| D | speculation.txt | 9 employ speculative execution techniques such as branch prediction, performing
12 Typically speculative execution cannot be observed from architectural state,
|
| /Linux-v5.4/tools/perf/util/ |
| D | parse-events.l | 361 speculative-read|speculative-load |
|
| /Linux-v5.4/Documentation/ia64/ |
| D | aliasing.rst | 69 are speculative[2], so the processor can read any location in the
78 Uncacheable mappings are not speculative, so the processor will
201 WB-only memory, but since UC is non-speculative, the processor will
|
| D | fsys.rst | 244 handler performed a speculative load that gets NaTted. If so, this
|
| /Linux-v5.4/include/linux/ |
| D | bpf_verifier.h | 251 bool speculative; member
|
| /Linux-v5.4/arch/sh/ |
| D | Kconfig.cpu | 74 This enables support for a speculative instruction fetch for
|
| /Linux-v5.4/arch/s390/kernel/ |
| D | entry.S | 312 xgr %r1,%r1 # prevent speculative use
359 # clear user controlled register to prevent speculative use
650 # clear user controlled registers to prevent speculative use
726 # clear user controlled registers to prevent speculative use
955 # clear user controlled registers to prevent speculative use
1179 # clear user controlled registers to prevent speculative use
|
| /Linux-v5.4/Documentation/driver-api/mmc/ |
| D | mmc-async-req.rst | 10 It depends. Fast eMMC and multiple cache levels with speculative cache
|
| /Linux-v5.4/Documentation/filesystems/ext4/ |
| D | allocators.rst | 21 unused speculative allocations are of course freed, but if the
|
| /Linux-v5.4/Documentation/devicetree/bindings/reserved-memory/ |
| D | reserved-memory.txt | 58 nor permit speculative access to it under any circumstances other
|
| /Linux-v5.4/drivers/staging/most/Documentation/ |
| D | driver_usage.txt | 154 case of speculative configuration, the creation is post-poned until
175 In case of speculative configuration, the creation is post-poned
|
| /Linux-v5.4/arch/s390/ |
| D | Kconfig | 590 regard to speculative execution.
602 prompt "Avoid speculative indirect branches in the kernel"
605 against kernel-to-user data leaks by avoiding speculative indirect
|
| /Linux-v5.4/kernel/bpf/ |
| D | verifier.c | 737 dst_state->speculative = src->speculative; in copy_verifier_state()
805 bool speculative) in push_stack() argument
823 elem->st.speculative |= speculative; in push_stack()
4289 if (vstate->speculative) in sanitize_ptr_alu()
7068 if (old->speculative && !cur->speculative) in states_equal()
7482 state->speculative = false; in do_check()
7526 env->cur_state->speculative ? in do_check()
7547 env->cur_state->speculative ? in do_check()
|
| /Linux-v5.4/Documentation/translations/ko_KR/ |
| D | memory-barriers.txt | 396 유예, 메모리 오퍼레이션들의 조합, 예측적 로드(speculative load), 브랜치
397 예측(speculative branch prediction), 다양한 종류의 캐싱(caching) 등의 다양한
|
| /Linux-v5.4/arch/x86/kvm/ |
| D | mmu.c | 3046 gfn_t gfn, kvm_pfn_t pfn, bool speculative, in set_spte() argument
3069 if (!speculative) in set_spte()
3138 if (speculative) in set_spte()
3150 bool speculative, bool host_writable) in mmu_set_spte() argument
3184 speculative, true, host_writable); in mmu_set_spte()
|
| /Linux-v5.4/drivers/perf/ |
| D | xgene_pmu.c | 364 XGENE_PMU_EVENT_ATTR(mcu-rd-proceed-speculative-all, 0x19),
365 XGENE_PMU_EVENT_ATTR(mcu-rd-proceed-speculative-cancel, 0x1a),
|
| /Linux-v5.4/arch/arm/mm/ |
| D | Kconfig | 923 not perform speculative loads into the D-cache. For such
1096 on ARMv6 CPUs, but since they do not have aggressive speculative
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | xfs.rst | 258 with unused speculative preallocation runs. The scan
|
