Home
last modified time | relevance | path

Searched refs:to (Results 1 – 25 of 65) sorted by relevance

123

/tools/virtio/linux/
Duaccess.h28 static void volatile_memcpy(volatile char *to, const volatile char *from, in volatile_memcpy() argument
32 *(to++) = *(from++); in volatile_memcpy()
35 static inline int copy_from_user(void *to, const void __user volatile *from, in copy_from_user() argument
39 volatile_memcpy(to, from, n); in copy_from_user()
43 static inline int copy_to_user(void __user volatile *to, const void *from, in copy_to_user() argument
46 __chk_user_ptr(to, n); in copy_to_user()
47 volatile_memcpy(to, from, n); in copy_to_user()
/tools/lguest/
Dlguest.txt2 (___()'`; Rusty's Remarkably Unreliable Guide to Lguest
6 Lguest is designed to be a minimal 32-bit x86 hypervisor for the Linux kernel,
7 for Linux developers and users to experiment with virtualization with the
8 minimum of complexity. Nonetheless, it should have sufficient features to
9 make it useful for specific tasks, and, of course, you are encouraged to fork
16 - Simple program to create new guests.
21 - Fun to hack on.
22 - No ABI: being tied to a specific kernel anyway, you can change anything.
27 - The easiest way to run lguest is to use same kernel as guest and host.
28 You can configure them differently, but usually it's easiest not to.
[all …]
/tools/testing/ktest/examples/
DREADME1 This directory contains example configs to use ktest for various tasks.
2 The configs still need to be customized for your environment, but it
3 is broken up by task which makes it easier to understand how to set up
7 and commented to show more generic use cases that are more helpful for
12 it easy to compile test different archs. You can download the arch
17 used to perform real testing.
19 kvm.conf - A example of a config that is used to test a virtual guest running
22 snowball.conf - An example config that was used to demo ktest.pl against
27 to reuse configs for various machines or set ups. The files here
/tools/perf/Documentation/
Dandroid.txt1 How to compile perf for Android
9 1. You need to download and install the Android Native Development Kit (NDK).
10 Set the NDK variable to point to the path where you installed the NDK:
11 export NDK=/path/to/android-ndk
21 This method is not working for Android NDK versions up to Revision 8b.
32 2. Build your own NDK sysroot to contain latest bionic changes and set the
50 You need to run make with the NDK toolchain and sysroot defined above:
58 You need to connect to your Android device/emulator using adb.
62 If you also want to use perf-archive you need busybox tools for Android.
63 For installing perf-archive, you first need to replace #!/bin/bash with #!/system/bin/sh:
[all …]
Dperf-script.txt23 'perf script' to see a detailed trace of the workload that was
28 available via 'perf script -l'). The following variants allow you to
31 'perf script record <script> <command>' to record the events required
37 'perf script report <script> [args]' to run and display the results
41 record <script>' is used and should be present for this command to
42 succeed. [args] refers to the (mainly optional) args expected by
45 'perf script <script> <required-script-args> <command>' to both
46 record the events required for <script> and to run the <script>
47 using 'live-mode' i.e. without writing anything to disk. <script>
53 optional script args to be specified; if optional script args are
[all …]
Dperf-stat.txt29 (use 'perf list' to list all events) or a raw PMU
59 print large numbers with thousands' separators according to locale
66 to activate system-wide monitoring. Default is to count on all CPUs.
83 print counts using a CSV-style output to make it easy to import directly into
89 in per-cpu mode. The cgroup filesystem must be mounted. All threads belonging to
91 can be provided. Each cgroup is applied to the corresponding event, i.e., first cgroup
92 to first event, second cgroup to second event and so on. It is possible to provide
94 corresponding events, i.e., they always refer to events defined earlier on the command
102 Append to the output file designated with the -o option. Ignored if -o is not specified.
106 Log output to fd, instead of stderr. Complementary to --output, and mutually exclusive
[all …]
Dperf-script-perl.txt16 This perf script option is used to process perf script data using perf's
31 ~/libexec/perf-core/scripts/perl for typical examples showing how to
34 attempts to exercise all of the main scripting features.
42 ignored (or passed to a 'trace_handled' function, see below) and the
45 Most of the event's field values are passed as arguments to the
49 As an example, the following perf record command can be used to record
54 Traces meant to be processed using a script should be recorded with
55 the above option: -a to enable system-wide collection.
88 arguments passed to all event handlers; some of the fields correspond
89 to the common_* fields in the format file, but some are synthesized,
[all …]
Dperf-script-python.txt16 This perf script option is used to process perf script data using perf's
24 This section shows the process, start to finish, of creating a working
29 available to script writers.
31 This example actually details the steps that were used to create the
33 scripts via 'perf script -l'. As such, this script also shows how to
38 basic ideas necessary to create a useful script. Here's an example
73 Basically our task is to keep a per-syscall tally that gets updated
75 that, but first we need to record the data that will be processed by
82 useful if we want to later use the guidance we get from the
83 general-purpose scripts to drill down and get more detail about
[all …]
Dperf-list.txt23 more modifiers. Modifiers allow the user to restrict the events to be
38 2 - SAMPLE_IP requested to have 0 skid
42 which supports up to precise-level 2.
44 On AMD systems it is implemented using IBS (up to precise-level 2).
46 clocks not halted) and 0xC1 (micro-ops retired). Both events map to
50 Sampling). Examples to use IBS:
79 delivered by loop stream detector invert to count
87 You should refer to the processor specific documentation for getting these
97 . 'hw' or 'hardware' to list hardware events such as cache-misses, etc.
99 . 'sw' or 'software' to list software events such as context switches, etc.
[all …]
Dperf-buildid-cache.txt15 This command manages the build-id cache. It can add and remove files to/from
23 Add specified file to the cache.
32 Update specified file of the cache. It can be used to update kallsyms
33 kernel dso to vmlinux in order to support annotation.
Dperf-sched.txt6 perf-sched - Tool to trace/measure scheduler properties (latencies)
17 'perf sched record <command>' to record the scheduling events
20 'perf sched latency' to report the per task scheduling latencies
23 'perf sched script' to see a detailed trace of the workload that
24 was recorded (aliased to 'perf script' for now).
26 'perf sched replay' to simulate the workload that was recorded
33 'perf sched map' to print a textual context-switching outline of
Dperf-timechart.txt6 perf-timechart - Tool to visualize total system behavior during a workload
17 'perf timechart record <command>' to record the system level events
20 'perf timechart' to turn a trace into a Scalable Vector Graphics file,
39 Select the processes to display, by name or PID
42 Look for files with symbols relative to this directory.
Dperf-kvm.txt6 perf-kvm - Tool to trace/measure kvm guest os
21 'perf kvm [options] top <command>' to generates and displays
25 'perf kvm record <command>' to record the performance counter profile
31 'perf kvm report' to display the performance counter profile information
34 'perf kvm diff' to displays the performance difference amongst two perf.data
37 'perf kvm buildid-list' to display the buildids found in a perf data file,
38 so that other tools can be used to fetch packages with matching symbol tables
41 'perf kvm stat <command>' to run a command and gather performance counter
75 Guest os /proc/kallsyms file copy. 'perf' kvm' reads it to get guest
78 Guest os /proc/modules file copy. 'perf' kvm' reads it to get guest
[all …]
Dperf-record.txt31 - a symbolic event name (use 'perf list' to list all events)
37 where addr is the address in memory you want to break in.
40 If you want to profile read-write accesses in 0x1000, just set
73 Append to the output file to do incremental profiling.
81 Event period to sample.
120 Sample timestamps. Use it with 'perf report -D' to see the timestamps,
136 the thread executes on the designated CPUs. Default is to monitor all CPUs.
147 in per-cpu mode. The cgroup filesystem must be mounted. All threads belonging to
149 can be provided. Each cgroup is applied to the corresponding event, i.e., first cgroup
150 to first event, second cgroup to second event and so on. It is possible to provide
[all …]
Dperf-report.txt56 Only display entries resolved to a symbol.
70 - parent: name of function matched to the parent regex filter. Unmatched
84 - dso_to: name of library or module branched to
86 - symbol_to: name of function branched to
89 And default sort keys are changed to comm, dso_from, symbol_from, dso_to
94 A regex filter to identify parent. The parent is a caller of this
97 defaults to "\^sys_|^do_page_fault", see '--sort parent'.
105 Force each column width to the provided list, for large terminal
145 requires a tty, if one is not present, as when piping to other
167 Look for files with symbols relative to this directory.
[all …]
Djit-interface.txt1 perf supports a simple JIT interface to resolve symbols for dynamic code generated
4 The JIT has to write a /tmp/perf-%d.map (%d = pid of process) file
15 The ownership of the file has to match the process.
Dperf-kmem.txt6 perf-kmem - Tool to trace/measure kernel memory(slab) properties
17 'perf kmem record <command>' to record the kmem events
20 'perf kmem stat' to report kernel memory statistics.
/tools/power/cpupower/
DREADME18 tools and programs to the cpufreq core and drivers in the Linux kernel. This
20 the interaction to the cpufreq core, and support for both the sysfs and proc
33 /usr/bin, respectively. If you want to set up the paths differently and/or
34 want to configure the package to your specific needs, you need to open
41 Many thanks to Mattia Dongili who wrote the autotoolization and
43 to Dave Jones for his feedback and his dump_psb tool; to Bruno Ducrot for his
45 and to various others commenting on the previous (pre-)releases of
DToDo3 - Use bitmask functions to parse CPU topology more robust
5 - Try to read out boost states and frequencies on Intel
7 - Somewhere saw the ability to read power consumption of
/tools/perf/scripts/perl/Perf-Trace-Util/
DREADME9 that scripts may want to use. Context.pm contains the Perl->C
10 interface that allows scripts to access data in the embedding perf
11 executable; scripts wishing to do that should 'use Context.pm'.
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
17 that you want to access - it's passed as the second parameter,
18 $context, to all handler functions.
22 perl Makefile.PL # to create a Makefile for the next step
23 make # to create Context.c
25 edit Context.c to add const to the char* file = __FILE__ line in
[all …]
/tools/power/cpupower/bench/
DREADME-BENCH9 - Identify average reaction time of a governor to CPU load changes
27 cpufreq-bench helps to test the condition of a given cpufreq governor.
28 For that purpose, it compares the performance governor to a configured
56 takes on this machine and needs to be run in a loop using the performance
59 and the governor to test. The time the calculation really needed
73 For example if ondemand governor is configured to have a 50ms
103 Provide a gnuplot utility script for easy generation of plots to present
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
113 -c, --cpu=<unsigned int> CPU Number to use, starting at 0
[all …]
/tools/virtio/virtio-trace/
DREADME4 Trace agent is a user tool for sending trace data of a guest to a Host in low
6 - splice a page of ring-buffer to read_pipe without memory copying
7 - splice the page from write_pipe to virtio-console without memory copying
8 - write trace data to stdout by using -o option
13 2) Create a read/write thread per CPU. Each thread is bound to a CPU.
18 5) The read/write threads start to read trace data from ring-buffers and
19 write the data to virtio-serial.
21 stop to read trace data.
38 To use this trace agent for virtio-trace, we need to prepare some virtio-serial
42 virtio-trace uses virtio-serial pipe as trace data paths as to the number
[all …]
/tools/perf/
Ddesign.txt10 thus be used to profile the code that runs on that CPU.
29 VFS system calls: read() can be used to read the counter, fcntl()
30 can be used to set the blocking mode, etc.
115 If a CPU is not able to count the selected event, then the system call
119 and accessed as raw events. For example, to count "External bus
121 in a 0x4064 event_id value and set hw_event.raw_type to 1.
160 * Bits that can be set in hw_event.read_format to request that
170 particular counter allowing one to take the round-robin scheduling effect
174 A "sampling" counter is one that is set up to generate an interrupt
180 * Bits that can be set in hw_event.record_type to request information
[all …]
/tools/perf/config/
Dutilities.mak1 # This allows us to work with the newline character:
12 # This is used as the common way to specify
22 # GNU make's $(shell ...) function converts to a
27 # The only solution is to change each newline into
46 # Use this to escape newlines from within a shell call;
62 # Use this to unescape newlines from within a shell call;
110 # (this is in constrast to a `$(shell ...)' function call,
117 # If the text to be wordified contains a newline, then
119 # to render the text as a single line; when the shell
141 # (It's necessary to use `sh -c' because GNU make messes up by
[all …]
/tools/perf/util/
Dutil.c58 static int slow_copyfile(const char *from, const char *to) in slow_copyfile() argument
68 to_fp = fopen(to, "w"); in slow_copyfile()
85 int copyfile(const char *from, const char *to) in copyfile() argument
96 return slow_copyfile(from, to); in copyfile()
102 tofd = creat(to, 0755); in copyfile()
117 unlink(to); in copyfile()

123