| /tools/perf/util/ |
| D | pager.c | 18 fd_set in; in pager_preexec() local
21 FD_ZERO(&in); in pager_preexec()
23 FD_SET(0, &in); in pager_preexec()
25 select(1, &in, NULL, &exception, NULL); in pager_preexec()
72 pager_process.in = -1; in setup_pager()
79 dup2(pager_process.in, 1); in setup_pager()
81 dup2(pager_process.in, 2); in setup_pager()
82 close(pager_process.in); in setup_pager()
|
| D | run-command.c | 30 need_in = !cmd->no_stdin && cmd->in < 0; in start_command()
37 cmd->in = fdin[1]; in start_command()
47 else if (cmd->in) in start_command()
48 close(cmd->in); in start_command()
59 else if (cmd->in) in start_command()
60 close(cmd->in); in start_command()
78 } else if (cmd->in) { in start_command()
79 dup2(cmd->in, 0); in start_command()
80 close(cmd->in); in start_command()
127 else if (cmd->in) in start_command()
[all …]
|
| D | intlist.h | 22 void intlist__remove(struct intlist *ilist, struct int_node *in);
50 static inline struct int_node *intlist__next(struct int_node *in) in intlist__next() argument
53 if (!in) in intlist__next()
55 rn = rb_next(&in->rb_node); in intlist__next()
|
| /tools/perf/Documentation/ |
| D | Build.txt | 39 resulting in following objects:
40 $ ls *-in.o
41 gtk-in.o libperf-in.o perf-in.o
43 Those objects are then used in final linking:
44 libperf-gtk.so <- gtk-in.o libperf-in.o
45 perf <- perf-in.o libperf-in.o
|
| D | perf-script-python.txt | 17 built-in Python interpreter. It reads and processes the input file and
18 displays the results of the trace analysis implemented in the given
74 every time a system call occurs in the system. Our script will do
104 That single stream will be recorded in a file in the current directory
109 callback handler for each event type found in the perf.data trace
116 The output file created also in the current directory is named
117 perf-script.py. Here's the file in its entirety:
124 # in the format files. Those fields not available as handler params can
138 print "in trace_begin"
141 print "in trace_end"
[all …]
|
| D | perf-script-perl.txt | 17 built-in Perl interpreter. It reads and processes the input file and
18 displays the results of the trace analysis implemented in the given
25 -g perl' in the same directory as an existing perf.data trace file.
27 the event types in the trace file; it simply prints every available
28 field for each event in the trace file.
30 You can also look at the existing scripts in
40 'handler function' is called for each event in the trace. If there's
50 all sched_wakeup events in the system:
87 The $common_* arguments in the handler's argument list are the set of
89 to the common_* fields in the format file, but some are synthesized,
[all …]
|
| D | perf-buildid-list.txt | 6 perf-buildid-list - List the buildids in a perf.data file
15 This command displays the buildids found in a perf.data file, so that other
19 It can also be used to show the build id of the running kernel or in an ELF
|
| D | perf-stat.txt | 23 Any command you can specify in a shell.
32 - a raw PMU event (eventsel+umask) in the form of rNNN where NNN is a
40 param1 and param2 are defined as formats for the PMU in
44 where M, N, K are numbers (in decimal, hex, octal format).
46 parameters are defined by corresponding entries in
94 Do not aggregate counts across all monitored CPUs in system-wide mode (-a).
95 This option is only valid in system-wide mode.
108 spreadsheets. Columns are separated by the string specified in SEP.
112 monitor only in the container (cgroup) called "name". This option is available only
113 in per-cpu mode. The cgroup filesystem must be mounted. All threads belonging to
[all …]
|
| D | perf-record.txt | 25 Any command you can specify in a shell.
33 - a raw PMU event (eventsel+umask) in the form of rNNN where NNN is a
41 'param1', 'param2', etc are defined as formats for the PMU in
46 where M, N, K are numbers (in decimal, hex, octal format). Acceptable
48 corresponding entries in /sys/bus/event_sources/devices/<pmu>/format/*
49 param1 and param2 are defined as formats for the PMU in:
52 There are also some params which are not defined in .../<pmu>/format/*.
67 - a hardware breakpoint event in the form of '\mem:addr[/len][:access]'
68 where addr is the address in memory you want to break in.
72 If you want to profile read-write accesses in 0x1000, just set
[all …]
|
| D | perf-mem.txt | 24 queueing delays in addition to the memory subsystem latency.
29 Any command you can specify in a shell.
37 Dump the raw decoded samples on the screen in a format that is easy to parse with
48 option can be passed in record mode. It will be interpreted the same way as perf
|
| D | perf-report.txt | 41 Only consider symbols in these comms. CSV that understands
51 Only consider symbols in these dsos. CSV that understands
70 in CSV format. Following sort keys are available:
92 - overhead_sys: Overhead percentage of sample running in system mode
93 - overhead_us: Overhead percentage of sample running in user mode
94 - overhead_guest_sys: Overhead percentage of sample running in system mode
96 - overhead_guest_us: Overhead percentage of sample running in user mode on
113 - in_tx: branch in TSX transaction
115 - cycles: Cycles in basic block
122 Specify output field - multiple keys can be specified in CSV format.
[all …]
|
| D | perf-top.txt | 15 This command generates and displays a performance counter profile in real time.
42 event (eventsel+umask) in the form of rNNN where NNN is a
84 Record events in threads owned by uid. Name or number.
120 Please see description of --sort in the perf-report man page.
123 Specify output field - multiple keys can be specified in CSV format.
128 By default, every sort keys not specified in --field will be appended
139 Only consider symbols in these dsos. This option will affect the
143 Only consider symbols in these comms. This option will affect the
165 implies -g. See `--call-graph` section in perf-record and
170 show up in the output. The output will have a new "Children" column
[all …]
|
| /tools/virtio/virtio-trace/ |
| D | README | 4 Trace agent is a user tool for sending trace data of a guest to a Host in low
41 1) Make FIFO in a host
45 # mkfifo /tmp/virtio-trace/trace-path-cpu{0,1,2,...,X}.{in,out}
46 # mkfifo /tmp/virtio-trace/agent-ctl-path.{in,out}
49 trace-path-cpu{0,1,2}.{in.out}
51 agent-ctl-path.{in,out}.
53 2) Set up of virtio-serial pipe in a host
87 You can find some chardev in /dev/virtio-ports/ in the guest.
93 0) Build trace agent in a guest
96 1) Enable ftrace in the guest
[all …]
|
| /tools/usb/usbip/ |
| D | .gitignore | 2 Makefile.in
7 config.h.in
15 libsrc/Makefile.in
20 src/Makefile.in
|
| D | INSTALL | 20 those values to create a `Makefile' in each directory of the package.
23 you can run in the future to recreate the current configuration, and a
35 diffs or instructions to the address given in the `README' so they can
40 The file `configure.ac' (or `configure.in') is used to create
67 all sorts of other programs in order to regenerate files that came
81 by setting variables in the command line or in the environment. Here
92 same time, by placing the object files for each architecture in their
96 source code in the directory that `configure' is in and in `..'.
99 architecture at a time in the source code directory. After you have
120 you can set and what kinds of files go in them.
[all …]
|
| /tools/vm/ |
| D | slabinfo-gnuplot.sh | 154 check_file_exist "$in"
158 out=`basename "$in"`"-slabs-by-loss"
159 `cat "$in" | grep -A "$lines" 'Slabs sorted by loss' |\
167 out=`basename "$in"`"-slabs-by-size"
168 `cat "$in" | grep -A "$lines" 'Slabs sorted by size' |\
175 out=`basename "$in"`"-totals"
176 `cat "$in" | grep "Memory used" |\
|
| /tools/build/Documentation/ |
| D | Build.txt | 36 called $(OBJECT)-in.o:
38 $ ls $(DIR)/$(OBJECT)-in.o
40 which includes all compiled sources described in 'Build' makefiles.
71 ex-y += b.o # duplicates in the lists are allowed
88 ex/ex-in.o
89 ex/libex-in.o
91 that contain request objects names in Build files.
95 $ ar rcs libex.a libex-in.o
96 $ gcc -o ex ex-in.o libex.a
98 You can check the 'ex' example in 'tools/build/tests/ex' for more details.
[all …]
|
| /tools/power/cpupower/bench/ |
| D | README-BENCH | 34 You can specify load (100% CPU load) and sleep (0% CPU load) times in us which
35 will be run X time in a row (cycles):
56 takes on this machine and needs to be run in a loop using the performance
83 But if ondemand always kicks in in the middle of the load sleep cycles, it
97 governor in average behaves as expected.
109 -l, --load=<long int> initial load time in us
110 -s, --sleep=<long int> initial sleep time in us
111 -x, --load-step=<long int> time to be added to load time, in us
112 -y, --sleep-step=<long int> time to be added to sleep time, in us
123 After the benchmark, the logfile is saved in OUTPUTDIR/benchmark_TIMESTAMP.log
|
| /tools/power/cpupower/ |
| D | README | 16 tools and programs to the cpufreq core and drivers in the Linux kernel. This
17 allows for code reduction in userspace tools, a clean implementation of
29 should suffice on most systems. It builds libcpupower to put in
30 /usr/lib; cpupower, cpufreq-bench_plot.sh to put in /usr/bin; and
31 cpufreq-bench to put in /usr/sbin. If you want to set up the paths
|
| /tools/testing/selftests/rcutorture/doc/ |
| D | initrd.txt | 2 in order to allow an initrd to be built into your kernel. The trick
3 here is to steal the initrd file used on your Linux laptop, Ubuntu in
17 need userspace in many cases. Running without userspace has the
19 distro in place, the root-filesystem layout, and so on. To make this
20 happen, put the following script in the initrd's tree's "/init" file,
75 for i in /sys/devices/system/cpu/cpu*/online
77 case $i in
|
| /tools/testing/selftests/futex/ |
| D | README | 11 primitives. These can be used as is in user applications or can serve as
28 implemented in header files, avoiding the need to compile intermediate object
39 ERROR strings in color for easy visual parsing. Output shall conform to the
55 problem as we intend to write multiple tests which collide in this namespace.
57 detailed description in the test source and the output.
62 kernel as defined in the Linux source Documentation/CodingStyle.
|
| /tools/build/ |
| D | Build.include | 36 # Escape single quote for use in echo statements
47 # Replace >#< with >$(pound)< to avoid starting a comment in the .cmd file
49 # Replace >'< with >'\''< to be able to enclose the whole string in '...'
55 # PHONY targets skipped in both cases.
74 # dependencies in the cmd file
87 # C flags to be used in rule definitions, includes:
|
| /tools/thermal/tmon/ |
| D | README | 17 matrix by hand is not a trivial task. Testing is also difficult in that
18 thermal conditions are often exception cases that hard to reach in
41 -c, --control cooling device in control
47 -g, --debug debug message in syslog
|
| /tools/lguest/ |
| D | lguest.txt | 14 - Kernel module which runs in a normal kernel.
52 - A tool called "lguest" is available in this directory: type "make"
53 to build it. If you didn't build your kernel in-tree, use "make
66 Make sure that you install a getty on /dev/hvc0 if you want to log in on the
77 64: the amount of memory to use, in MB.
79 vmlinux: the kernel image found in the top of your build directory. You
118 /dev/hwrng in the guest that will read from the host's /dev/random.
119 Use this option in conjunction with rng-tools (see ../hw_random.txt)
|
| /tools/perf/scripts/perl/Perf-Trace-Util/ |
| D | README | 10 interface that allows scripts to access data in the embedding perf
14 want to add new Perl functions that end up accessing C data in the
16 scripting_context is a pointer to the perf data in the perf executable
25 edit Context.c to add const to the char* file = __FILE__ line in
37 module in the right place.
|