Home
last modified time | relevance | path

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

12345678910>>...12

/tools/virtio/linux/
Duaccess.h30 static void volatile_memcpy(volatile char *to, const volatile char *from, in volatile_memcpy() argument
34 *(to++) = *(from++); in volatile_memcpy()
37 static inline int copy_from_user(void *to, const void __user volatile *from, in copy_from_user() argument
41 volatile_memcpy(to, from, n); in copy_from_user()
45 static inline int copy_to_user(void __user volatile *to, const void *from, in copy_to_user() argument
48 __chk_user_ptr(to, n); in copy_to_user()
49 volatile_memcpy(to, from, n); in copy_to_user()
/tools/lib/traceevent/Documentation/
Dlibtraceevent-reg_event_handler.txt7 unregisters a callback function to parse an event information.
29 which is going to be called to parse the information for a given event.
32 the event belongs to. The _event_name_ argument is the name of the event.
33 If _id_ is >= 0, it is used to find the event, otherwise _sys_name_ and
34 _event_name_ are used. The _func_ is a pointer to the function, which is going
35 to be called to parse the event information. The _context_ argument is a pointer
36 to the context data, which will be passed to the _func_. If a handler function
38 one. This mechanism allows a developer to override the parsing of a given event.
40 can register a function for an event to be used to parse the data instead.
49 function. The _s_ argument is the trace sequence, it can be used to create a
[all …]
Dlibtraceevent-reg_print_func.txt33 This allows a plugin to dynamically create a way to process one of
38 to the helper function. The _ret_type_ argument is the return type of the
50 the trace sequence, it can be used to create a custom string.
74 Notice the call to function _yesno()_ in the print arguments. In the kernel
86 The user space event parser has no idea how to handle this _yesno()_ function.
87 The _tep_register_print_function()_ API can be used to register a user space
88 helper function, mapped to the kernel's _yesno()_:
107 /* Failed to register yes_no_helper function */
112 how to handle it.
116 /* Failed to unregister yes_no_helper function */
[all …]
Dlibtraceevent-tseq.txt32 Trace sequences are used to allow a function to call several other functions
33 to create a string of data to use.
58 The _trace_seq_do_printf()_ function prints the buffer of trace sequence _s_ to
62 to the given file _fp_.
91 /* Failed to print in the trace sequence */
100 /* Failed to put str in the trace sequence */
103 /* Failed to put ':' 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 */
[all …]
Dlibtraceevent-field_print.txt24 These functions print recorded field's data, according to the field's type.
27 the _field_ and prints it into _s_, according to the field type.
30 value according to the field's type:
41 _s_, according to the given format string _fmt_. If the argument _err_ is
47 to be a function address, and a search is perform to find the name of this
49 according to the given format string _fmt_. If the argument _err_ is non-zero,
96 Header file to include in order to have access to the library APIs.
98 Header file to include in order to have access to trace sequences related APIs.
99 Trace sequences are used to allow a function to call several other functions
100 to create a string of data to use.
[all …]
Dlibtraceevent-func_apis.txt27 Some tools may have already a way to resolve the kernel functions. These APIs
28 allow them to keep using it instead of duplicating all the entries inside.
31 functions resolver. This function receives a pointer to its custom context
33 function, which has to be resolved. In case of success, it should return
40 _tep_find_function_address()_, and _tep_print_func_field()_ to resolve
41 a function address to a function name.
44 resolver to the default function. The _tep_ argument is trace event parser
48 These APIs can be used to find function name and start address, by given
49 address. The given address does not have to be exact, it will select
56 by given address _addr_. The _addr_ does not have to be exact, it will select
[all …]
Dlibtraceevent-event_print.txt22 _record_ and writes it into the trace sequence _s_, according to the format
40 N : The task is set to call the scheduler when
42 may need to be scheduled in.
43 . : The task is not set to call the scheduler.
61 (lock depth, or migration disabled, which are unique to
100 Header file to include in order to have access to the library APIs.
102 Header file to include in order to have access to trace sequences related APIs.
103 Trace sequences are used to allow a function to call several other functions
104 to create a string of data to use.
106 Linker switch to add when building a program that uses the library.
[all …]
Dlibtraceevent-parse_head.txt21 _buf_ is with _size_, and is supposed to be copied from
25 _tep_parse_header_page()_ function can be called with _size_ equal to 0. The
27 this use case, to set the size of a long integer to be used.
46 /* Failed to parse the header page */
56 Header file to include in order to have access to the library APIs.
58 Linker switch to add when building a program that uses the library.
74 Report bugs to <linux-trace-devel@vger.kernel.org>
/tools/power/cpupower/
DREADME16 tools and programs to the cpufreq core and drivers in the Linux kernel. This
18 the interaction to the cpufreq core, and support for both the sysfs and proc
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
32 differently and/or want to configure the package to your specific
33 needs, you need to open "Makefile" with an editor of your choice and
39 Many thanks to Mattia Dongili who wrote the autotoolization and
41 to Dave Jones for his feedback and his dump_psb tool; to Bruno Ducrot for his
43 and to various others commenting on the previous (pre-)releases of
/tools/testing/selftests/kvm/lib/x86_64/
Dhandlers.S51 .macro HANDLERS has_error from to argument
53 .rept \to - \from + 1
73 HANDLERS has_error=0 from=0 to=7
74 HANDLERS has_error=1 from=8 to=8
75 HANDLERS has_error=0 from=9 to=9
76 HANDLERS has_error=1 from=10 to=14
77 HANDLERS has_error=0 from=15 to=16
78 HANDLERS has_error=1 from=17 to=17
79 HANDLERS has_error=0 from=18 to=255
/tools/testing/selftests/arm64/fp/
Dassembler.h8 .macro __for from:req, to:req
9 .if (\from) == (\to)
12 __for \from, %(\from) + ((\to) - (\from)) / 2
13 __for %(\from) + ((\to) - (\from)) / 2 + 1, \to
17 .macro _for var:req, from:req, to:req, insn:vararg
25 __for \from, \to
/tools/usb/usbip/
DINSTALL8 unlimited permission to copy, distribute and modify it.
16 instructions specific to this package.
18 The `configure' shell script attempts to guess correct values for
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
29 the results of its tests to speed up reconfiguring. Caching is
30 disabled by default to prevent problems with accidental use of stale
33 If you need to do unusual things to compile the package, please try
34 to figure out how `configure' could check whether to do them, and mail
35 diffs or instructions to the address given in the `README' so they can
[all …]
DCOPYING6 Everyone is permitted to copy and distribute verbatim copies
11 The licenses for most software are designed to take away your
12 freedom to share and change it. By contrast, the GNU General Public
13 License is intended to guarantee your freedom to share and change free
14 software--to make sure the software is free for all its users. This
15 General Public License applies to most of the Free Software
16 Foundation's software and to any other program whose authors commit to
18 the GNU Library General Public License instead.) You can apply it to
21 When we speak of free software, we are referring to freedom, not
22 price. Our General Public Licenses are designed to make sure that you
[all …]
DREADME8 USB/IP protocol allows to pass USB device from server to client over the
11 The USB device may be either physical device connected to a server or
17 and allows to import a USB device from a remote machine.
21 bound to a physical USB device to make it exportable.
25 to export a USB device created using USB Gadget Subsystem.
28 A set of userspace tools used to handle connection and management.
63 First of them is physical usb device connected to the machine.
78 - Bind usbip-host.ko to the device with busid 1-2.
79 - The USB device 1-2 is now exportable to other hosts!
80 - Use `usbip unbind --busid 1-2' to stop exporting the device.
[all …]
/tools/perf/Documentation/
Dperf-ftrace.txt18 just reads trace_pipe in text and then write it to stdout.
20 The following options apply to perf ftrace.
27 Tracer to use when neither -G nor -F option is not
36 List available functions to trace. It accepts a pattern to
48 Time (ms) to wait before starting tracing after program start.
54 normally don't - this option allows the latter to be run in
62 Default is to trace on all online CPUs.
66 Set the size of per-cpu tracing buffer, <size> is expected to
77 can be a glob pattern. It will be passed to 'set_ftrace_filter'
83 argument. Like -T option, this can be used more than once to
[all …]
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
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:
70 Some perf features need environment variables to run properly.
[all …]
/tools/perf/util/
Dcopyfile.c14 static int slow_copyfile(const char *from, const char *to, struct nsinfo *nsi) in slow_copyfile() argument
28 to_fp = fopen(to, "w"); in slow_copyfile()
73 static int copyfile_mode_ns(const char *from, const char *to, mode_t mode, in copyfile_mode_ns() argument
90 if (asprintf(&tmp, "%s.XXXXXXx", to) < 0) { in copyfile_mode_ns()
126 err = link(tmp, to); in copyfile_mode_ns()
133 int copyfile_ns(const char *from, const char *to, struct nsinfo *nsi) in copyfile_ns() argument
135 return copyfile_mode_ns(from, to, 0755, nsi); in copyfile_ns()
138 int copyfile_mode(const char *from, const char *to, mode_t mode) in copyfile_mode() argument
140 return copyfile_mode_ns(from, to, mode, NULL); in copyfile_mode()
143 int copyfile(const char *from, const char *to) in copyfile() argument
[all …]
/tools/bpf/bpftool/Documentation/
Dbpftool-cgroup.rst40 List all programs attached to the cgroup *CGROUP*.
54 The output is similar to the output of cgroup show/list
63 Attach program *PROG* to the cgroup *CGROUP* with attach type
67 some bpf program, the program in this cgroup yields to sub-cgroup
69 that cgroup program gets run in addition to the program in this
72 Only one program is allowed to be attached to a cgroup with
76 Multiple programs are allowed to be attached to a cgroup with
89 **bind4** call to bind(2) for an inet4 socket (since 4.17);
90 **bind6** call to bind(2) for an inet6 socket (since 4.17);
93 **connect4** call to connect(2) for an inet4 socket (since 4.17);
[all …]
/tools/testing/selftests/tc-testing/
DTODO.txt6 - Add support for multiple versions of tc to run successively
9 need to better handle problems in pre- and post-suite.
13 - Allow tdc to write its results to file.
17 will attempt to run a function at every hook point. Could be
18 changed so that plugin __init__ methods will register functions to
21 trying to run a function that will do nothing.
28 and a way to configure a test suite,
29 to automate running multiple "test suites" with different requirements
/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/testing/selftests/arm64/signal/
DREADME8 enforces a standard sequence of operations needed to perform a single
17 to run each test unit in its own standalone process, so as to start each
21 tdescr overriding all the defaults we wish to change (as of now providing a
24 - Signals' test-cases hereafter defined belong currently to two
32 is placed on the stack and a sigreturn syscall is called to simulate a
38 kind of tests it is extremely easy in fact to end-up injecting other
39 unrelated SEGV bugs in the testcases, it becomes extremely tricky to
41 to address and they are not instead falling apart due to unplanned bugs
43 In order to alleviate the misery of the life of such test-developer, a few
46 - a couple of ASSERT_BAD/GOOD_CONTEXT() macros to easily parse a ucontext_t
[all …]
/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/testing/selftests/net/forwarding/
DREADME5 to easily create and test complex environments.
8 ASICs, as their ports can not be migrated to other network namespaces
26 The VRFs act as lightweight namespaces representing hosts connected to
30 traditional method that requires multiple physical machines, to name a
36 2. Ability to easily provision complex topologies. Testing bridging
38 not always available. With the VRF-based approach one merely needs to
42 on any Linux box using veth pairs to emulate physical loopbacks.
51 o Where possible, IPv6 and IPv4 addresses shall conform to RFC 3849 and
54 multiple topologies and added to lib.sh.
55 o Checks shall be added to lib.sh for any external dependencies.
[all …]
/tools/objtool/Documentation/
Dstack-validation.txt19 alternative execution paths to a given instruction (or set of
20 instructions). Similarly, it knows how to follow switch statements, for
36 code and debug tools to be able to walk the stack to determine the
37 chain of function call sites that led to the currently executing
42 required by the ABI (sometimes referred to as "backchain pointers").
47 But for asm code, the frame setup instructions have to be written by
51 For stack traces based on frame pointers to be reliable, all
85 skipped. Instead the stack trace seems to show that
99 An alternative to frame pointers and DWARF, ORC unwind data can be
100 used to walk the stack. Unlike frame pointers, ORC data is out of
[all …]
/tools/memory-model/Documentation/
Dexplanation.txt47 for people who want to understand how the model was designed. It does
63 end. Converting them to the right format is left as an exercise for
76 In practice, people tend to use memory models the other way around.
79 code to run in such a way that the loads will indeed obtain the
87 systems, with multiple CPUs making concurrent accesses to shared
91 kernel supports a variety of architectures. The LKMM has to be fairly
93 architectures also has to be allowed by the LKMM.
99 Here is a simple example to illustrate the basic concepts. Consider
102 device, stores it in a buffer, and sets a flag to indicate the buffer
105 system call. This code tests the flag to see whether the buffer is
[all …]

12345678910>>...12