| /linux/lib/ |
| H A D | Kconfig.kasan | 19 Disables both inline and stack instrumentation. Selected by
20 architectures that do not support these instrumentation types.
142 prompt "Instrumentation type"
147 bool "Outline instrumentation"
154 bool "Inline instrumentation"
164 bool "Stack instrumentation (unsafe)" if CC_IS_CLANG && !COMPILE_TEST
169 Disables stack instrumentation and thus KASAN's ability to detect
172 With Clang, stack instrumentation has a problem that causes excessive
179 With GCC, enabling stack instrumentation is assumed to be safe.
181 If the architecture disables inline instrumentation via
[all …]
|
| H A D | Kconfig.kmsan | 18 instrumentation provided by Clang and thus requires Clang to build.
38 is a more relaxed mode, but it generates more instrumentation code and
|
| H A D | Kconfig.kcsan | 21 data-race detector that relies on compile-time instrumentation.
197 Weak memory modeling relies on additional instrumentation and may
|
| H A D | Kconfig.ubsan | 10 Compile-time instrumentation is used to detect various undefined
22 text on failure paths. To avoid this, Sanitizer instrumentation
112 # seeing UBSan instrumentation located in unreachable places.
|
| /linux/Documentation/trace/rv/ |
| H A D | da_monitor_instrumentation.rst | 1 Deterministic Automata Instrumentation
5 includes a section dedicated to instrumentation.
10 * This is the instrumentation part of the monitor.
47 instrumentation section translates *kernel events* into the *model's
123 They should be used to *attach* and *detach* the instrumentation to the running
135 Instrumentation helpers
138 To complete the instrumentation, the *handler functions* need to be attached to a
|
| /linux/Documentation/dev-tools/ |
| H A D | kasan.rst | 53 Software KASAN modes use compile-time instrumentation to insert validity checks
93 ``CONFIG_KASAN_INLINE``. Outline and inline are compiler instrumentation types.
311 safe to access and use compile-time instrumentation to insert shadow memory
329 Compile-time instrumentation is used to insert memory access checks. Compiler
334 With inline instrumentation, instead of making function calls, the compiler
357 Software Tag-Based KASAN uses compile-time instrumentation to insert checks
363 Software Tag-Based KASAN also has two instrumentation modes (outline, which
365 memory checks inline). With outline instrumentation mode, a bug report is
367 instrumentation, a ``brk`` instruction is emitted by the compiler, and a
378 hardware memory tagging support instead of compiler instrumentation and
[all …]
|
| /linux/Documentation/arch/powerpc/ |
| H A D | kasan.txt | 11 Instrumentation of the vmalloc area is optional, unless built with modules,
23 - It would be good to support inline instrumentation so as to be able to catch
26 - Inline instrumentation requires a fixed offset.
38 One approach is just to give up on inline instrumentation. This way boot-time
|
| /linux/include/linux/ |
| H A D | kcsan-checks.h | 18 #define KCSAN_ACCESS_COMPOUND (1 << 1) /* Compounded read-write instrumentation. */
20 /* The following are special, and never due to compiler instrumentation. */
50 * __kcsan_mb - full memory barrier instrumentation
55 * __kcsan_wmb - write memory barrier instrumentation
60 * __kcsan_rmb - read memory barrier instrumentation
65 * __kcsan_release - release barrier instrumentation
218 * instrumentation enabled. May be used in header files.
237 * Normal barrier instrumentation is not done via explicit calls, but by mapping
240 * like any other compile-time instrumentation, barrier instrumentation can be
|
| H A D | kasan-checks.h | 9 * KASAN modes that rely on compiler instrumentation, and will be optimized
34 * instrumentation enabled. May be used in header files.
|
| H A D | compiler_types.h | 130 * Note: This may conflict with instrumentation inserted on function entry which
277 * to __no_sanitize_* in compilation units where instrumentation is enabled
279 * instrumentation (__SANITIZE_*__ undefined).
296 * Clang still emits instrumentation for __tsan_func_{entry,exit}() and builtin
299 * want any instrumentation with __no_kcsan.
302 * disable all instrumentation. See Kconfig.kcsan where this is mandatory.
418 * 2) supressing instrumentation around where cpuidle disables RCU; where the
|
| /linux/Documentation/devicetree/bindings/iio/amplifiers/ |
| H A D | adi,ada4250.yaml | 7 title: ADA4250 Programmable Gain Instrumentation Amplifier
13 Precision Low Power, 110kHz, 26uA, Programmable Gain Instrumentation Amplifier.
|
| /linux/mm/kmsan/ |
| H A D | Makefile | 6 obj-y := core.o instrumentation.o init.o hooks.o report.o shadow.o
12 # Disable instrumentation of KMSAN runtime with other tools.
|
| H A D | instrumentation.c | 8 * instrumentation works.
44 * KMSAN instrumentation functions follow. They are not declared elsewhere in
133 * KMSAN instrumentation pass replaces LLVM memcpy, memmove and memset
|
| /linux/kernel/kcsan/ |
| H A D | core.c | 445 * all be inlinable by the instrumentation functions.
451 * since they do not access any user memory, but instrumentation is still
726 * for constant sized instrumentation (__tsan_{read,write}N). in check_access()
979 * KCSAN uses the same instrumentation that is emitted by supported compilers
982 * When enabled, the compiler emits instrumentation calls (the functions
1126 * instrumentation is inserted before the real access, a data in __tsan_func_exit()
1147 * Instrumentation for atomic builtins (__atomic_*, __sync_*).
1155 * etc.), implementing the ARCH_ATOMIC interface (to get instrumentation via
1158 * TSAN instrumentation replaces atomic accesses with calls to any of the below
1286 * In instrumented files, we emit instrumentation for barriers by mapping the
[all …]
|
| /linux/Documentation/devicetree/bindings/arm/ |
| H A D | arm,coresight-stm.yaml | 24 primarily for high-bandwidth trace of instrumentation embedded into software.
25 This instrumentation is made up of memory-mapped writes to the STM Advanced
|
| /linux/kernel/bpf/ |
| H A D | Kconfig | 93 bool "Enable BPF LSM Instrumentation"
99 Enables instrumentation of the security hooks with BPF programs for
|
| /linux/tools/verification/rvgen/rvgen/templates/dot2k/ |
| H A D | main.c | 8 #include <rv/instrumentation.h>
34 * This is the instrumentation part of the monitor.
|
| /linux/tools/verification/rvgen/rvgen/templates/ltl2k/ |
| H A D | main.c | 8 #include <rv/instrumentation.h>
51 * This is the instrumentation part of the monitor.
|
| /linux/arch/powerpc/platforms/pseries/ |
| H A D | hvCall_inst.c | 5 * Hypervisor Call Instrumentation
19 /* For hcall instrumentation. One structure per-hcall, per-CPU */
|
| /linux/scripts/ |
| H A D | Makefile.kasan | 31 # call threshold number, the compiler will use inline instrumentation.
58 kasan_params += asan-instrumentation-with-call-threshold=$(call_threshold) \
|
| /linux/kernel/trace/ |
| H A D | Makefile | 9 # Avoid recursion due to instrumentation.
13 # selftest needs instrumentation
|
| /linux/include/asm-generic/bitops/ |
| H A D | instrumented-non-atomic.h | 4 * This file provides wrappers with sanitizer instrumentation for non-atomic
79 * Use generic write instrumentation, in case other sanitizers in __instrument_read_write_bitop()
|
| /linux/scripts/atomic/ |
| H A D | gen-atomic-instrumented.sh | 138 * This file provoides atomic operations with explicit instrumentation (e.g.
140 * instrumentation. Where it is necessary to aovid instrumenation, the
|
| /linux/arch/s390/tools/ |
| H A D | gen_facilities.c | 118 196, /* processor activity instrumentation facility */
119 197, /* processor activity instrumentation extension 1 */
|
| /linux/arch/x86/kernel/cpu/microcode/ |
| H A D | core.c | 372 * Protected against instrumentation up to the point where the primary
399 * Protected against instrumentation up to the point where the primary
547 * Protection against instrumentation is required for CPUs which are not
549 * while the primary thread updates the microcode. Instrumentation can end
553 * The primary thread is safe versus instrumentation as the actual
|