Home
last modified time | relevance | path

Searched refs:at (Results 1 – 25 of 83) sorted by relevance

1234

/tools/testing/selftests/rcutorture/doc/
DTREE_RCU-kconfig.txt24 CONFIG_RCU_EQS_DEBUG -- Do at least one for CONFIG_NO_HZ_FULL and not.
32 nohz_full - do at least one.
33 maxcpu -- do at least one.
34 rcupdate.rcu_self_test_bh -- Do at least one each, offloaded and not.
35 rcupdate.rcu_self_test_sched -- Do at least one each, offloaded and not.
36 rcupdate.rcu_self_test -- Do at least one each, offloaded and not.
37 rcutree.rcu_fanout_exact -- Do at least one.
/tools/testing/selftests/tc-testing/
DTODO.txt17 will attempt to run a function at every hook point. Could be
20 require action at a specific point, no penalty will be paid for
/tools/memory-model/litmus-tests/
DMP+poonceonces.litmus7 * no ordering at all?
DSB+poonceonces.litmus6 * This litmus test demonstrates that at least some ordering is required
DWRC+poonceonces+Once.litmus8 * test has no ordering at all.
DIRIW+poonceonces+OnceOnce.litmus7 * between each pairs of reads. In other words, is anything at all
/tools/perf/Documentation/
Dperf-report.txt82 - dso: name of library or module executed at the time of sample
83 - dso_size: size of library or module executed at the time of sample
84 - symbol: name of function executed at the time of sample
85 - symbol_size: size of function executed at the time of sample
88 - cpu: cpu number the task ran at the time of sample
89 - socket: processor socket number the task ran at the time of sample
90 - srcline: filename and line number executed at the time of sample. The
144 - symbol_daddr: name of data symbol being executed on at the time of sample
146 on at the time of the sample
147 - locked: whether the bus was locked at the time of the sample
[all …]
DBuild.txt67 supported by GCC. UBSan detects undefined behaviors of programs at runtime.
73 If UBSan detects any problem at runtime, it outputs a “runtime error:” message.
Djitdump-specification.txt128 * uint32_t line : source file line number (starting at 1)
133 They need to be walked sequentially. The next debug_entry is found at sizeof(debug_entry) + strlen(…
158 uint64_t unwind_data_size : the size in bytes of the unwinding data table at the end of the record
159 …size : the size in bytes of the DWARF EH Frame Header at the start of the unwinding data table at…
164 …s the Linux Standard Base (LSB) specification as described in the document at https://refspecs.lin…
167 The EH Frame follows the LSB specicfication as described in the document at https://refspecs.linuxb…
Dtopdown.txt115 to read slots and the topdown metrics at different points of the program:
136 Then the program can be instrumented to read these metrics at different
167 read at the same time.
170 measured at different points, and determine the metrics
216 So as long as the reading is at reasonable intervals (every few
Dperf-record.txt141 - 'start': defines an address at which tracing will begin.
142 - 'stop': defines an address at which tracing will stop.
223 Profile at this frequency. Use 'max' to use the currently maximum
269 doesn't work with branch stack sampling at the same time.
374 - u: only when the branch target is at the user level
376 - hv: only when the target is at the hypervisor level
384 The option requires at least one branch type among any, any_call, any_ret, ind_call, cond.
420 Capture machine state (registers) at interrupt, i.e., on counter overflows for
428 Similar to -I, but capture user registers at sample time. To list the available
446 'e': take one last snapshot on exit; guarantees that there is at least one
[all …]
/tools/testing/selftests/firmware/
Dsettings6 # of the 3 configs, so at least another 15 seconds are needed. Add another
/tools/testing/kunit/test_data/
Dtest_is_test_passed-failure.log27 # example_simple_test: EXPECTATION FAILED at lib/kunit/example-test.c:30
/tools/lib/traceevent/Documentation/
Dlibtraceevent-func_find.txt52 /* addr is in function named fname, starting at fstart address, at offset (addr - fstart) */
Dlibtraceevent-event_get.txt21 The _tep_get_event()_ function returns a pointer to event at the given _index_.
34 The _tep_get_event()_ returns a pointer to the event located at _index_.
Dlibtraceevent-func_apis.txt72 which has an address needs to know what string would be at that address. The
76 The _addr_ is the address the string was located at.
132 addr is in function named fname, starting at fstart address,
133 at offset (addr - fstart)
Dlibtraceevent-plugins.txt32 - System's plugin directory, defined at the library compile time. It
36 - User's plugin directory, located at _~/.local/lib/traceevent/plugins_
/tools/usb/usbip/
DREADME201 : (Defined at Interface level) / unknown subclass / unknown protocol (00/00/00)
206 : (Defined at Interface level) / unknown subclass / unknown protocol (00/00/00)
211 : (Defined at Interface level) / unknown subclass / unknown protocol (00/00/00)
216 : (Defined at Interface level) / unknown subclass / unknown protocol (00/00/00)
229 Port 00: <Port in Use> at Full Speed(12Mbps)
/tools/testing/selftests/tc-testing/plugin-lib/
DREADME-PLUGINS24 deleted at the end of the run.
/tools/testing/selftests/rcutorture/bin/
Dkvm-test-1-run.sh46 echo ' ---' Kconfig fragment at: $config_template >> $resdir/log
275 echo "!!! PID $qemu_pid hung at $kruntime vs. $seconds seconds" >> $resdir/Warnings 2>&1
/tools/objtool/Documentation/
Dstack-validation.txt9 objtool which runs at compile time. It has a "check" subcommand which
15 validates the correct frame pointer state at each instruction.
92 [*] unless an interrupt or exception has occurred at the very
94 or at the very end of the function after the stack frame has been
114 source tree at Documentation/livepatch/livepatch.rst.
157 because it only analyzes a single file at a time.
262 pushes and sets up the frame pointer (for x86_64, this means rbp) at
263 the beginning of the function and pops it at the end of the function.
331 is not at the beginning of a function. If this is a legit call, you
/tools/testing/selftests/drivers/net/mlxsw/
Dqos_lib.sh66 configure Qdiscs. mlxsw does not support both at the
/tools/testing/selftests/zram/
DREADME11 Statistics for individual zram devices are exported through sysfs nodes at
/tools/testing/selftests/lkdtm/
Dtests.txt2 BUG kernel BUG at
/tools/memory-model/Documentation/
Dsimple.txt25 In single-threaded code, there is no reordering, at least assuming
29 CPUs at the same time. One important exception is a function that makes
35 that you acquire at the beginning of your code and release at the end,
38 this lock at a given time, your code will be executed single-threaded.
213 hence they do not provide any ordering guarantees at all.
269 If the alternatives above do not do what you need, please look at the

1234