| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | uprobe_syscall_executed.c | 12 int executed = 0; variable
21 executed++; in BPF_UPROBE()
31 executed++; in BPF_URETPROBE()
41 executed++; in test_uprobe_multi()
51 executed++; in test_uretprobe_multi()
61 executed++; in test_uprobe_session()
71 executed++; in test_usdt()
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | uprobe_syscall.c | 335 ASSERT_EQ(skel->bss->executed, 0, "executed"); in test_uretprobe_syscall_call()
407 void *addr, int executed) in check_attach() argument
419 /* Make sure bpf program got executed.. */ in check_attach()
420 ASSERT_EQ(skel->bss->executed, executed, "executed"); in check_attach()
439 trigger_t trigger, void *addr, int executed) in check() argument
443 tramp = check_attach(skel, trigger, addr, executed); in check()
476 skel->bss->executed in test_uprobe_legacy()
[all...] |
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-online | 10 .offline() callback is executed for the device and (if
13 this file, the device bus type's .online() callback is executed
20 type's .online() is executed successfully.
|
| H A D | sysfs-driver-ppi | 31 executed in the pre-OS environment. It is the only input from
60 operation to be executed in the pre-OS environment by the BIOS
71 operation to be executed in the pre-OS environment by the BIOS
|
| /linux/Documentation/tools/rtla/ |
| H A D | common_options.txt | 68 Defines an action to be executed when tracing is stopped on a latency threshold
71 Multiple --on-threshold actions may be specified, and they will be executed in
73 will not be executed.
94 Continue tracing after actions are executed instead of stopping.
112 Defines an action to be executed at the end of tracing.
114 Multiple --on-end actions can be specified, and they will be executed in the order
116 executed.
|
| /linux/lib/kunit/ |
| H A D | Kconfig | 100 string only matching tests are executed.
102 If unsure, leave empty so all tests are executed.
108 string only matching tests are executed.
110 If unsure, leave empty so all tests are executed.
116 string only matching tests are executed.
118 If unsure, leave empty so all tests are executed.
|
| /linux/tools/testing/selftests/tc-testing/creating-testcases/ |
| H A D | AddingTestCases.txt | 41 dependsOn: Same as 'skip', but the value is executed as a command. The test
49 Each command can be a string to be executed, or a list consisting
50 of a string which is a command to be executed, followed by 1 or
70 Each command can be a string to be executed, or a list consisting
71 of a string which is a command to be executed, followed by 1 or
|
| /linux/Documentation/livepatch/ |
| H A D | callbacks.rst | 63 callback will only be executed if its corresponding patch callback was
64 executed. Typical use cases pair a patch handler that acquires and
68 A callback is only executed if its host klp_object is loaded. For
90 No post-patch, pre-unpatch, or post-unpatch callbacks will be executed
96 will only occur if their corresponding post-patch callback executed).
|
| /linux/Documentation/driver-api/pm/ |
| H A D | notifiers.rst | 38 executed and tasks have been thawed.
47 callbacks have been executed and tasks have been thawed.
54 resume callbacks have been executed and tasks have been thawed.
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-mem.txt | 106 - symbol_daddr: name of data symbol being executed on at the time of sample
107 - symbol_iaddr: name of code symbol being executed on at the time of sample
108 - dso_daddr: name of library or module containing the data being executed
115 - phys_daddr: physical address of data being executed on at the time of sample
116 - data_page_size: the data page size of data being executed on at the time of sample
|
| H A D | perf-ftrace.txt | 110 functions executed from the given function. This can be used more
119 executed from the given function. This can be used more than once to
192 useful to trace for functions executed from the given function. This
200 disables tracing for function executed from the given function. This
|
| H A D | perf-report.txt | 98 - dso: name of library or module executed at the time of sample
99 - dso_size: size of library or module executed at the time of sample
100 - symbol: name of function executed at the time of sample
101 - symbol_size: size of function executed at the time of sample
107 - srcline: filename and line number executed at the time of sample. The
172 executed, such as a memory access bottleneck. If a function has high overhead
179 - symbol_daddr: name of data symbol being executed on at the time of sample
180 - dso_daddr: name of library or module containing the data being executed
187 - phys_daddr: physical address of data being executed on at the time of sample
188 - data_page_size: the data page size of data being executed on at the time of sample
|
| /linux/Documentation/arch/arm/ |
| H A D | kernel_mode_neon.rst | 13 * Don't sleep in your NEON code, and be aware that it will be executed with
24 may call schedule()], as NEON or VFP instructions will be executed in a
58 * NEON/VFP code is executed with preemption disabled.
75 executed in kernel mode. If such a condition is encountered, the kernel will
|
| /linux/Documentation/power/ |
| H A D | suspend-and-interrupts.rst | 14 ->prepare, ->suspend and ->suspend_late callbacks have been executed for all
52 for it will be executed as usual after suspend_device_irqs(), even if the
91 not executed for system wakeup IRQs. They are only executed for IRQF_NO_SUSPEND
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | special-register-buffer-data-sampling.rst | 59 executed on another core or sibling thread using MDS techniques.
87 the mitigation for RDRAND and RDSEED instructions executed outside of Intel
103 disables the mitigation for RDRAND and RDSEED executed outside of an Intel SGX
|
| /linux/drivers/mtd/ubi/ |
| H A D | fastmap-wl.c | 112 int free, expect_free, executed; in wait_free_pebs_for_pool() local
135 if (do_work(ubi, &executed) || !executed) in wait_free_pebs_for_pool()
|
| /linux/tools/memory-model/litmus-tests/ |
| H A D | MP+polockonce+poacquiresilsil.litmus | 9 * the smp_load_acquire() executed before the lock was acquired (loosely
|
| H A D | MP+polockmbonce+poacquiresilsil.litmus | 10 * executed before the lock was acquired (loosely speaking).
|
| /linux/kernel/debug/kdb/ |
| H A D | kdb_cmds | 2 # These commands are executed in kdb_init() context, no SMP, no
|
| /linux/Documentation/tee/ |
| H A D | op-tee.rst | 134 * Attack vector: Code that is executed prior to issuing the SMC call to load
145 load OP-TEE isn't executed when desired, leaving it open to being executed
|
| /linux/arch/arm/boot/compressed/ |
| H A D | head-xscale.S | 20 @ This is done by fetching through currently executed
|
| H A D | head-sa1100.S | 30 @ This is done by fetching through currently executed
|
| /linux/net/rds/ |
| H A D | Kconfig | 35 are executed.
|
| /linux/tools/memory-model/Documentation/ |
| H A D | explanation.txt | 105 the driver code being executed by a process in the midst of a read(2)
185 if each CPU executed its instructions in order but with unspecified
190 by each load is simply the value written by the most recently executed
363 (unless it can prove the accesses will never be executed), it will not
399 executed before either of the stores to y. However, a compiler could
412 from x could be executed after the store to y. Thus, the memory
793 time it is executed.) The memory subsystem also determines where the
819 Note that load instructions may be executed speculatively and may be
854 propagates stores. When a fence instruction is executed on CPU C:
860 a release fence is executed (including all po-earlier
[all …]
|
| /linux/Documentation/networking/devlink/ |
| H A D | devlink-selftests.rst | 12 the tests to be executed.
|