| /linux/Documentation/admin-guide/hw-vuln/ |
| H A 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 …]
|
| H A D | tsx_async_abort.rst | 6 TAA is a hardware vulnerability that allows unprivileged speculative access to 29 microprocessors utilizing speculative execution may
|
| H A D | gather_data_sampling.rst | 7 speculative access to data which was previously stored in vector registers.
|
| H A 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
|
| H A D | rsb.rst | 254 …verflow <https://www.amd.com/content/dam/amd/en/documents/corporate/cr/speculative-return-stack-ov…
|
| /linux/Documentation/ABI/testing/ |
| H A D | configfs-most | 59 creation of the link. In case of speculative 114 creation of the link. In case of speculative 169 creation of the link. In case of speculative 235 creation of the link. In case of speculative
|
| /linux/arch/alpha/lib/ |
| H A 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)
|
| H A 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/Documentation/staging/ |
| H A D | speculation.rst | 11 employ speculative execution techniques such as branch prediction, performing 14 Typically speculative execution cannot be observed from architectural state,
|
| /linux/fs/afs/ |
| H A D | dir_silly.c | 87 op->more_files[0].speculative = true; in afs_do_silly_rename() 89 op->more_files[1].speculative = true; in afs_do_silly_rename()
|
| H A D | dir.c | 859 vp->speculative = true; /* vnode not locked */ in afs_do_lookup() 2110 op->more_files[0].speculative = true; in afs_rename() 2112 op->more_files[1].speculative = true; in afs_rename()
|
| H A D | inode.c | 398 if (vp->speculative && in afs_vnode_commit_status()
|
| H A D | internal.h | 854 bool speculative:1; /* T if speculative status fetch (no vnode lock) */ member
|
| /linux/arch/sh/ |
| H A D | Kconfig.cpu | 69 This enables support for a speculative instruction fetch for
|
| /linux/Documentation/driver-api/mmc/ |
| H A D | mmc-async-req.rst | 10 It depends. Fast eMMC and multiple cache levels with speculative cache
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | allocators.rst | 21 unused speculative allocations are of course freed, but if the
|
| /linux/drivers/staging/most/Documentation/ |
| H A 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/tools/perf/Documentation/ |
| H A D | perf-arm-spe.txt | 107 The coarse effect of conversions, and, if applicable, sampling of speculative operations, can be 167 bit 1 - Instruction retired (i.e. omit speculative instructions)
|
| /linux/arch/s390/ |
| H A D | Kconfig | 609 regard to speculative execution. 622 prompt "Avoid speculative indirect branches in the kernel" 625 against kernel-to-user data leaks by avoiding speculative indirect
|
| /linux/tools/testing/selftests/bpf/ |
| H A D | README.rst | 145 verifier to understand such speculative pointer arithmetic.
|
| /linux/kernel/bpf/ |
| H A D | verifier.c | 1767 dst_state->speculative = src->speculative; in copy_verifier_state() 1974 if (!st->speculative) { in maybe_exit_scc() 2124 bool speculative) in push_stack() argument 2143 elem->st.speculative |= speculative; in push_stack() 14594 if (vstate->speculative) in sanitize_ptr_alu() 14674 if (!vstate->speculative) in sanitize_mark_insn_seen() 15017 && !env->cur_state->speculative in adjust_ptr_min_max_vals() 20149 if (old->speculative && !cur->speculative) in states_equal() 20963 env->insn_idx, env->cur_state->speculative); in check_indirect_jump() 21186 env->cur_state->speculative ? in do_check() [all …]
|
| /linux/net/sched/ |
| H A D | Kconfig | 377 The Remus HA project uses this module to enable speculative execution
|
| /linux/arch/arm/mm/ |
| H A D | Kconfig | 1108 on ARMv6 CPUs, but since they do not have aggressive speculative
|
| /linux/Documentation/ |
| H A D | memory-barriers.txt | 368 deferral and combination of memory operations; speculative loads; speculative
|
| /linux/arch/arm/ |
| H A D | Kconfig | 696 r3p*) erratum. A speculative memory access may cause a page table walk
|