Home
last modified time | relevance | path

Searched refs:print (Results 1 – 25 of 53) sorted by relevance

123

/tools/testing/selftests/size/
Dget_size.c35 static int print(const char *s) in print() function
65 return print(num_to_str(num, num_buf, sizeof(num_buf))); in print_num()
73 print(s); in print_k_value()
79 print("\n"); in print_k_value()
91 print("TAP version 13\n"); in _start()
92 print("# Testing system size.\n"); in _start()
96 print("not ok 1"); in _start()
97 print(test_name); in _start()
98 print(" ---\n reason: \"could not get sysinfo\"\n ...\n"); in _start()
101 print("ok 1"); in _start()
[all …]
/tools/lib/traceevent/Documentation/
Dlibtraceevent-set_flag.txt30 _TEP_NSEC_OUTPUT_ - print event's timestamp in nano seconds, instead of micro seconds.
64 /* print timestamps in nanoseconds */
66 /* print timestamps in microseconds */
Dlibtraceevent-parse_event.txt48 buf = read_file("/sys/kernel/tracing/events/ftrace/print/format", &size);
50 /* Failed to parse the ftrace print format */
54 /* Failed to parse the ftrace print format */
Dlibtraceevent-reg_print_func.txt32 Some events may have helper functions in the print format arguments.
40 of the helper function, as seen in the print format arguments. The _..._ is a
64 Some events have internal functions calls, that appear in the print format
68 print fmt: "pipe %c, frame=%u, scanline=%u, wm %d/%d/%d, sr %s/%d/%d/%d, hpll %s/%d/%d/%d, fbc %s",
74 Notice the call to function _yesno()_ in the print arguments. In the kernel
Dlibtraceevent-tseq.txt91 /* Failed to print in the trace sequence */
106 /* Failed to print in the trace sequence */
114 /* Failed to print the sequence buffer to the standard output */
118 /* Failed to print the sequence buffer to the trace.txt file */
Dlibtraceevent-field_print.txt24 These functions print recorded field's data, according to the field's type.
55 on success, -1 in case of an error or 0 if the print buffer _s_ is full.
Dlibtraceevent-func_apis.txt145 if (tep_register_print_string(tep, "print string",
147 /* Failed to register "print string" address mapping */
/tools/perf/Documentation/
Dperf-script-python.txt138 print "in trace_begin"
141 print "in trace_end"
149 print "id=%d, args=%s\n" % \
153 print ' '.join(['%s=%s'%(k,str(v))for k,v in sorted(event_fields_dict.items())])
156 print "%-20s %5u %05u.%09u %8u %-20s " % \
223 print "in trace_end"
230 In trace_end(), we'll simply print the results, but first we need to
231 generate some results to print. To do that we need to have our
301 print "\nsyscall events for %s:\n\n" % (for_comm),
303 print "\nsyscall events:\n\n",
[all …]
Dperf-stat.txt88 print more detailed statistics, can be specified up to 3 times
96 repeat command and print average + stddev (max: 100). 0 means forever.
100 print large numbers with thousands' separators according to locale
123 print counts using a CSV-style output to make it easy to import directly into
178 --interval-print msecs::
192 Stop the 'perf stat' session and print count deltas after N milliseconds (minimum: 10 ms).
197 Only print computed metrics. Print them in a single line.
Dperf-config.txt115 print-type = graph
248 this option lets 'annotate' print a list of assembly code with the source code.
393 call-graph.print-type::
394 The print-types can be graph (graph absolute), fractal (graph relative),
420 This option controls print order of callchains. The default is
437 When there're many callchains it'd print tons of lines. So perf omits
440 by value depends on call-graph.print-type.
442 call-graph.print-limit::
Dperf-trace.txt208 --print-sample::
225 dumps just boolean map values and integer keys, in time this will print in hex
240 fault); if no debug symbols available, perf trace will print raw IP;
250 When --verbose specified, perf trace tries to print all available information
/tools/perf/util/
Dheader.h106 void (*print)(struct feat_fd *ff, FILE *fp); member
/tools/perf/ui/browsers/
Dhists.c797 print_callchain_entry_fn print, in hist_browser__show_callchain_list() argument
836 print(browser, chain, str, offset, row, arg); in hist_browser__show_callchain_list()
861 print_callchain_entry_fn print, in hist_browser__show_callchain_flat() argument
894 print, arg); in hist_browser__show_callchain_flat()
917 print, arg); in hist_browser__show_callchain_flat()
965 print_callchain_entry_fn print, in hist_browser__show_callchain_folded() argument
1033 print(browser, first_chain, chain_str, offset, row++, arg); in hist_browser__show_callchain_folded()
1050 print_callchain_entry_fn print, in hist_browser__show_callchain_graph() argument
1087 print, arg); in hist_browser__show_callchain_graph()
1102 print, arg, is_output_full); in hist_browser__show_callchain_graph()
[all …]
/tools/bpf/bpftool/Documentation/
Dbpftool-feature.rst49 print warnings to kernel logs.
/tools/power/pm-graph/config/
Dfreeze.cfg17 # print verbose messages (default: false)
Dstandby.cfg17 # print verbose messages (default: false)
Dsuspend-x2-proc.cfg17 # print verbose messages (default: false)
Dfreeze-callgraph.cfg18 # print verbose messages (default: false)
Dsuspend-dev.cfg17 # print verbose messages (default: false)
Dsuspend.cfg17 # print verbose messages (default: false)
Dstandby-callgraph.cfg18 # print verbose messages (default: false)
Dfreeze-dev.cfg17 # print verbose messages (default: false)
Dsuspend-callgraph.cfg18 # print verbose messages (default: false)
Dstandby-dev.cfg17 # print verbose messages (default: false)
/tools/testing/selftests/futex/
DREADME38 sent to stderr. Tests shall support the -c option to print PASS, FAIL, and

123