Searched refs:how (Results 1 – 25 of 40) sorted by relevance
12
| /tools/perf/util/ |
| D | ordered-events.c | 266 static int __ordered_events__flush(struct ordered_events *oe, enum oe_flush how, in __ordered_events__flush() argument
283 switch (how) { in __ordered_events__flush()
320 str[how], oe->nr_events); in __ordered_events__flush()
326 if (how == OE_FLUSH__ROUND) in __ordered_events__flush()
329 oe->last_flush_type = how; in __ordered_events__flush()
333 str[how], oe->nr_events); in __ordered_events__flush()
339 int ordered_events__flush(struct ordered_events *oe, enum oe_flush how) in ordered_events__flush() argument
341 return __ordered_events__flush(oe, how, 0); in ordered_events__flush()
|
| D | ordered-events.h | 58 int ordered_events__flush(struct ordered_events *oe, enum oe_flush how);
|
| /tools/testing/ktest/examples/ |
| D | README | 3 is broken up by task which makes it easier to understand how to set up
26 included into other configs. This is a real use example that shows how
|
| /tools/perf/Documentation/ |
| D | perf-inject.txt | 40 Merge sched_stat and sched_switch for getting events where and how long
42 sched_stat contains a timeslice how long a task slept.
|
| D | build-xed.txt | 2 For --xed the xed tool is needed. Here is how to install it:
|
| D | perf-timechart.txt | 30 There are also poll bars which show how much time application spent
|
| D | perf-diff.txt | 115 Determine how to display the overhead percentage of filtered entries.
249 relative to how entries are filtered. Use --percentage=absolute to
|
| D | perf-list.txt | 36 Print how named events are resolved internally into perf events, and also
59 The 'p' modifier can be used for specifying how precise the instruction
|
| D | examples.txt | 173 Or observe how fluctuating the page allocations are, via statistical
|
| D | intel-pt.txt | 32 and how did software get to a certain point, or behave a certain way. The
141 There is also script intel-pt-events.py which provides an example of how to
327 mtc_period Specifies how frequently MTC packets are produced - see mtc
328 above for how to determine if MTC packets are supported.
372 cyc_thresh Specifies how frequently CYC packets are produced - see cyc
373 above for how to determine if CYC packets are supported.
|
| D | perf-probe.txt | 191 See EXAMPLES how it is used.
222 and 'ALN2' is end line number in the file. It is also possible to specify how
|
| D | perf-script-python.txt | 33 scripts via 'perf script -l'. As such, this script also shows how to
92 don't care how it exited, so we'll use 'perf record' to record only
425 ~/libexec/perf-core/scripts/python for typical examples showing how to
|
| /tools/memory-model/litmus-tests/ |
| D | Z6.0+pooncelock+poonceLock+pombonce.litmus | 6 * This litmus test demonstrates how smp_mb__after_spinlock() may be
|
| D | MP+polocks.litmus | 6 * This litmus test demonstrates how lock acquisitions and releases can
|
| D | MP+porevlocks.litmus | 6 * This litmus test demonstrates how lock acquisitions and releases can
|
| /tools/io_uring/ |
| D | README | 1 This directory includes a few programs that demonstrate how to use io_uring
|
| /tools/lib/traceevent/Documentation/ |
| D | libtraceevent-reg_print_func.txt | 86 The user space event parser has no idea how to handle this _yesno()_ function.
112 how to handle it.
|
| /tools/testing/fault-injection/ |
| D | failcmd.sh | 31 specifies how many times failures may happen at most.
|
| /tools/perf/lib/Documentation/tutorial/ |
| D | tutorial.rst | 48 how to create it and display its cpus:
|
| /tools/power/cpupower/bench/ |
| D | README-BENCH | 55 First it is calibrated how long a specific CPU intensive calculation
|
| /tools/testing/selftests/android/ion/ |
| D | README | 12 This utility demonstrates how ION buffer sharing can be implemented between
|
| /tools/build/Documentation/ |
| D | Build.txt | 5 idea and the way how objects are built is the same.
|
| /tools/usb/usbip/ |
| D | INSTALL | 34 to figure out how `configure' could check whether to do them, and mail
204 `configure' recognizes the following options to control how it operates.
|
| /tools/lib/bpf/ |
| D | README.rst | 76 kernel source tree on how to use XDP sockets and for some common
|
| /tools/objtool/Documentation/ |
| D | stack-validation.txt | 20 instructions). Similarly, it knows how to follow switch statements, for
180 they mean, and suggestions for how to fix them.
|
12