Home
last modified time | relevance | path

Searched refs:speculative (Results 1 – 25 of 28) sorted by relevance

12

/linux/Documentation/admin-guide/hw-vuln/
H A Dspectre.rst7 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 Dtsx_async_abort.rst6 TAA is a hardware vulnerability that allows unprivileged speculative access to
29 microprocessors utilizing speculative execution may
H A Dgather_data_sampling.rst7 speculative access to data which was previously stored in vector registers.
H A Dl1tf.rst5 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 Drsb.rst254 …verflow <https://www.amd.com/content/dam/amd/en/documents/corporate/cr/speculative-return-stack-ov…
/linux/Documentation/ABI/testing/
H A Dconfigfs-most59 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 Dev67-strchr.S59 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 Dev6-memset.S166 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 Dspeculation.rst11 employ speculative execution techniques such as branch prediction, performing
14 Typically speculative execution cannot be observed from architectural state,
/linux/arch/sh/
H A DKconfig.cpu69 This enables support for a speculative instruction fetch for
/linux/kernel/bpf/
H A Dstates.c206 if (!st->speculative) { in maybe_exit_scc()
995 if (old->speculative && !cur->speculative) in states_equal()
H A Dverifier.c1668 dst_state->speculative = src->speculative; in bpf_copy_verifier_state()
1766 * occur during speculative verification. For these we can insert a in error_recoverable_with_nospec()
1769 * architectural path once it has been recovered-from in all speculative in error_recoverable_with_nospec()
1777 bool speculative) in push_stack() argument
1797 elem->st.speculative |= speculative; in push_stack()
1807 * 1. speculative states will bump 'branches' for non-branch in push_stack()
4119 * just checking it here would be insufficient as speculative stack in check_stack_read()
4120 * writes could still lead to unsafe speculative behaviou in check_stack_read()
[all...]
/linux/Documentation/driver-api/mmc/
H A Dmmc-async-req.rst10 It depends. Fast eMMC and multiple cache levels with speculative cache
/linux/Documentation/filesystems/ext4/
H A Dallocators.rst21 unused speculative allocations are of course freed, but if the
/linux/tools/perf/Documentation/
H A Dperf-arm-spe.txt107 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 DKconfig616 regard to speculative execution.
629 prompt "Avoid speculative indirect branches in the kernel"
632 against kernel-to-user data leaks by avoiding speculative indirect
/linux/fs/afs/
H A Ddir.c856 vp->speculative = true; /* vnode not locked */ in afs_do_lookup()
2124 op->more_files[0].speculative = true; in afs_rename()
2126 op->more_files[1].speculative = true; in afs_rename()
H A Dinode.c320 if (vp->speculative && in afs_vnode_commit_status()
H A Dinternal.h862 bool speculative:1; /* T if speculative status fetch (no vnode lock) */ member
/linux/tools/testing/selftests/bpf/
H A DREADME.rst145 verifier to understand such speculative pointer arithmetic.
/linux/drivers/perf/
H A Dxgene_pmu.c350 XGENE_PMU_EVENT_ATTR(mcu-rd-proceed-speculative-all, 0x19),
351 XGENE_PMU_EVENT_ATTR(mcu-rd-proceed-speculative-cancel, 0x1a),
/linux/include/linux/
H A Dbpf_verifier.h511 bool speculative; member
/linux/Documentation/process/
H A Dsecurity-bugs.rst203 speculative implications. Have your tool read this documentation as
/linux/net/sched/
H A DKconfig377 The Remus HA project uses this module to enable speculative execution
/linux/Documentation/
H A Dmemory-barriers.txt368 deferral and combination of memory operations; speculative loads; speculative

12