Searched full:instrumentation (Results 1 – 25 of 165) sorted by relevance
1234567
| /Linux-v6.1/include/linux/ |
| D | instrumented.h | 4 * This header provides generic wrappers for memory access instrumentation that
19 * Instrument a regular read access. The instrumentation should be inserted
34 * Instrument a regular write access. The instrumentation should be inserted
49 * Instrument a regular write access. The instrumentation should be inserted
64 * Instrument an atomic read access. The instrumentation should be inserted
79 * Instrument an atomic write access. The instrumentation should be inserted
94 * Instrument an atomic read-write access. The instrumentation should be
110 * variants). The instrumentation must be inserted before the accesses.
125 * instrument_copy_from_user_before - add instrumentation before copy_from_user
128 * variants). The instrumentation should be inserted before the accesses.
[all …]
|
| 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
|
| 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.
|
| D | instrumentation.h | 9 /* Begin/end of an instrumentation safe region */
21 * When the value is greater than 0, we consider instrumentation allowed.
|
| D | compiler_types.h | 196 * to __no_sanitize_* in compilation units where instrumentation is enabled
198 * instrumentation (__SANITIZE_*__ undefined).
215 * Clang still emits instrumentation for __tsan_func_{entry,exit}() and builtin
218 * want any instrumentation with __no_kcsan.
221 * disable all instrumentation. See Kconfig.kcsan where this is mandatory.
|
| /Linux-v6.1/lib/ |
| D | Kconfig.kasan | 19 Disables both inline and stack instrumentation. Selected by
20 architectures that do not support these instrumentation types.
126 prompt "Instrumentation type"
131 bool "Outline instrumentation"
138 bool "Inline instrumentation"
148 bool "Stack instrumentation (unsafe)" if CC_IS_CLANG && !COMPILE_TEST
153 Disables stack instrumentation and thus KASAN's ability to detect
156 With Clang, stack instrumentation has a problem that causes excessive
163 With GCC, enabling stack instrumentation is assumed to be safe.
165 If the architecture disables inline instrumentation via
[all …]
|
| D | Kconfig.ubsan | 9 Compile-time instrumentation is used to detect various undefined
22 text on failure paths. To avoid this, Sanitizer instrumentation
99 # seeing UBSan instrumentation located in unreachable places.
133 bool "Enable instrumentation for the entire kernel"
137 This option activates instrumentation for the entire kernel.
|
| D | Kconfig.kcsan | 20 data-race detector that relies on compile-time instrumentation.
188 # atomics instrumentation in .noinstr.text, or use a compiler that can
189 # implement __no_kcsan to really remove all instrumentation.
202 Weak memory modeling relies on additional instrumentation and may
|
| D | Kconfig.kmsan | 21 instrumentation provided by Clang and thus requires Clang to build.
47 is a more relaxed mode, but it generates more instrumentation code and
|
| /Linux-v6.1/Documentation/trace/rv/ |
| 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
|
| D | da_monitor_synthesis.rst | 10 *monitor* connects to the system via an *instrumentation* that converts
26 | (instrumentation) | | (verification) | | (specification) |
64 the system instrumentation.
137 dot2k, the developer's work should be limited to the instrumentation
|
| /Linux-v6.1/Documentation/dev-tools/ |
| D | kasan.rst | 50 Software KASAN modes use compile-time instrumentation to insert validity checks
90 ``CONFIG_KASAN_INLINE``. Outline and inline are compiler instrumentation types.
264 safe to access and use compile-time instrumentation to insert shadow memory
282 Compile-time instrumentation is used to insert memory access checks. Compiler
287 With inline instrumentation, instead of making function calls, the compiler
310 Software Tag-Based KASAN uses compile-time instrumentation to insert checks
316 Software Tag-Based KASAN also has two instrumentation modes (outline, which
318 memory checks inline). With outline instrumentation mode, a bug report is
320 instrumentation, a ``brk`` instruction is emitted by the compiler, and a
331 hardware memory tagging support instead of compiler instrumentation and
[all …]
|
| D | kmsan.rst | 9 values. It is based on compiler instrumentation, and is quite similar to the
81 Disabling the instrumentation
117 the only compiler that has KMSAN support. The kernel instrumentation pass is
135 instrumentation code inserted by the compiler (unless it is a stack variable
139 Compiler instrumentation also tracks the shadow values as they are used along
140 the code. When needed, instrumentation code invokes the runtime library in
220 Clang instrumentation API
223 Clang instrumentation pass inserts calls to functions defined in
282 Clang's MemorySanitizer instrumentation has an option,
316 Inline assembly instrumentation
|
| /Linux-v6.1/Documentation/powerpc/ |
| 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-v6.1/mm/kmsan/ |
| 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.
|
| /Linux-v6.1/drivers/gpu/drm/i915/gt/shaders/clear_kernel/ |
| D | hsw.asm | 23 * DW 1.3 - Enable Instrumentation (only for debug)
32 * BTI 1: Wait/Instrumentation Buffer
58 …align1 1N }; /* g3.2 now points to EU row number (Y-pixel = V address ) in instrumentation surf */
70 /* Media block read to fetch current value at specified location in instrumentation buffer */
76 /* Media block write for updated value at specified location in instrumentation buffer */
|
| D | ivb.asm | 23 * DW 1.3 - Enable Instrumentation (only for debug)
32 * BTI 1: Wait/Instrumentation Buffer
58 …align1 1N }; /* g3.2 now points to EU row number (Y-pixel = V address ) in instrumentation surf */
70 /* Media block read to fetch current value at specified location in instrumentation buffer */
75 /* Media block write for updated value at specified location in instrumentation buffer */
|
| /Linux-v6.1/Documentation/devicetree/bindings/iio/amplifiers/ |
| D | adi,ada4250.yaml | 7 title: ADA4250 Programmable Gain Instrumentation Amplifier
13 Precision Low Power, 110kHz, 26uA, Programmable Gain Instrumentation Amplifier.
|
| /Linux-v6.1/tools/verification/dot2/dot2k_templates/ |
| D | main_global.c | 8 #include <rv/instrumentation.h>
34 * This is the instrumentation part of the monitor.
|
| D | main_per_cpu.c | 8 #include <rv/instrumentation.h>
34 * This is the instrumentation part of the monitor.
|
| D | main_per_task.c | 8 #include <rv/instrumentation.h>
34 * This is the instrumentation part of the monitor.
|
| /Linux-v6.1/Documentation/devicetree/bindings/arm/ |
| 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-v6.1/kernel/bpf/ |
| D | Kconfig | 91 bool "Enable BPF LSM Instrumentation"
97 Enables instrumentation of the security hooks with BPF programs for
|
| /Linux-v6.1/kernel/kcsan/ |
| D | core.c | 434 * all be inlinable by the instrumentation functions.
440 * since they do not access any user memory, but instrumentation is still
715 * for constant sized instrumentation (__tsan_{read,write}N). in check_access()
968 * KCSAN uses the same instrumentation that is emitted by supported compilers
971 * When enabled, the compiler emits instrumentation calls (the functions
1115 * instrumentation is inserted before the real access, a data in __tsan_func_exit()
1136 * Instrumentation for atomic builtins (__atomic_*, __sync_*).
1144 * etc.), implementing the ARCH_ATOMIC interface (to get instrumentation via
1147 * TSAN instrumentation replaces atomic accesses with calls to any of the below
1273 * In instrumented files, we emit instrumentation for barriers by mapping the
[all …]
|
| /Linux-v6.1/arch/riscv/kernel/ |
| D | alternative.c | 96 * 2) The compiler instrumentation for FTRACE will not work for setup_vm()
97 * so disable compiler instrumentation when FTRACE is enabled.
|
1234567
