| /tools/testing/selftests/rcutorture/bin/ |
| D | kvm-find-errors.sh | 28 files=
34 files="$files $i.diags $i"
37 if test -n "$files"
39 $editor $files
49 files=
54 files="$files $i.diags $i"
57 if test -n "$files"
59 $editor $files
|
| D | parse-console.sh | 43 nerrs=`grep --binary-files=text '!!!' $file |
55 grep --binary-files=text 'torture:.*ver:' $file |
56 egrep --binary-files=text -v '\(null\)|rtc: 000000000* ' |
98 …echo $title no success message, `grep --binary-files=text 'ver:' $file | wc -l` successful version…
|
| D | kvm-recheck-rcu.sh | 43 …nclosecalls=`grep --binary-files=text 'torture: Reader Batch' $i/console.log | tail -1 | awk '{for…
|
| /tools/perf/util/ |
| D | data.c | 21 static void close_dir(struct perf_data_file *files, int nr) in close_dir() argument
24 close(files[nr].fd); in close_dir()
25 zfree(&files[nr].path); in close_dir()
27 free(files); in close_dir()
32 close_dir(data->dir.files, data->dir.nr); in perf_data__close_dir()
37 struct perf_data_file *files = NULL; in perf_data__create_dir() local
43 files = zalloc(nr * sizeof(*files)); in perf_data__create_dir()
44 if (!files) in perf_data__create_dir()
48 struct perf_data_file *file = &files[i]; in perf_data__create_dir()
62 data->dir.files = files; in perf_data__create_dir()
[all …]
|
| /tools/testing/selftests/pstore/ |
| D | pstore_post_reboot_tests | 53 files=`ls dmesg-${backend}-*`
54 operate_files $? "$files" grep_end_trace
77 files=`ls *-${backend}-*`
78 operate_files $? "$files" rm
|
| /tools/testing/selftests/cpufreq/ |
| D | cpufreq.sh | 48 local files=`ls $1`
52 for file in $files; do
80 local files=`ls $1`
84 for file in $files; do
|
| /tools/testing/selftests/proc/ |
| D | .gitignore | 6 /proc-self-map-files-001
7 /proc-self-map-files-002
|
| D | Makefile | 11 TEST_GEN_PROGS += proc-self-map-files-001
12 TEST_GEN_PROGS += proc-self-map-files-002
|
| /tools/testing/ktest/examples/ |
| D | README | 14 http://kernel.org/pub/tools/crosstool/files/bin/x86_64/
27 to reuse configs for various machines or set ups. The files here
28 are included by other config files, where the other config files define
|
| /tools/perf/Documentation/ |
| D | perf-archive.txt | 6 perf-archive - Create archive with object files with build-ids found in perf.data file
15 This command runs perf-buildid-list --with-hits, and collects the files with the
|
| D | perf-diff.txt | 6 perf-diff - Read perf.data files and display the differential profile
16 files captured via perf record.
21 specified perf.data files.
24 As the perf.data files could come from different binaries, the symbols addresses
25 could vary. So perf diff is based on the comparison of the files and
85 Look for files with symbols relative to this directory.
111 can be used only if enough data files are provided.
153 for different perf.data files.
183 file is iterated for samples. All other perf.data files specified on
187 All samples from non-baseline perf.data files, that do not match any
[all …]
|
| D | perf-buildid-cache.txt | 16 files to/from the cache. In the future it should as well set upper limits for
37 image. Note also that files "kallsyms" and "modules" must also be in the
38 same directory and are also copied. All 3 files are created with read
|
| D | perf-inject.txt | 58 Process jitdump files by injecting the mmap records corresponding to jitted
60 found in the jitdumps files captured in the input perf.data file. Use this option
|
| /tools/testing/selftests/filesystems/incfs/ |
| D | incfs_test.c | 60 struct test_file *files; member
74 static struct test_file files[] = { in get_test_files_set() local
106 return (struct test_files_set){ .files = files, in get_test_files_set()
107 .files_count = ARRAY_SIZE(files) }; in get_test_files_set()
112 static struct test_file files[] = { in get_small_test_files_set() local
128 return (struct test_files_set){ .files = files, in get_small_test_files_set()
129 .files_count = ARRAY_SIZE(files) }; in get_small_test_files_set()
632 bool same = same_id(&(test_set->files[j].id), in data_producer()
636 file = &test_set->files[j]; in data_producer()
1038 struct test_file *file = &test.files[i]; in basic_file_ops_test()
[all …]
|
| /tools/perf/ |
| D | CREDITS | 6 Here is an (incomplete!) list of main contributors to those files
30 The full history of the files can be found in the upstream Git commits.
|
| /tools/io_uring/ |
| D | README | 13 Benchmark program that does random reads on a number of files. This
14 app demonstrates the various features of io_uring, like fixed files,
16 control which features to use. Arguments is the file (or files) that
|
| D | io_uring-bench.c | 88 struct file files[MAX_FDS]; member
125 s->fds[i] = s->files[i].real_fd; in io_uring_register_files()
126 s->files[i].fixed_fd = i; in io_uring_register_files()
156 f = &s->files[0]; in init_io()
158 f = &s->files[s->cur_file]; in init_io()
163 f = &s->files[s->cur_file]; in init_io()
471 struct file *f = &s->files[i]; in file_depths()
511 f = &s->files[s->nr_files]; in main()
|
| /tools/usb/usbip/ |
| D | INSTALL | 21 It may also create one or more `.h' files containing system-dependent
31 cache files.
58 4. Type `make install' to install the programs and any data files and
61 5. You can remove the program binaries and object files from the
63 files that `configure' created (so you can compile the package for
67 all sorts of other programs in order to regenerate files that came
71 files again.
92 same time, by placing the object files for each architecture in their
94 directory where you want the object files and executables to go and run
107 `/usr/local/bin', include files under `/usr/local/include', etc. You
[all …]
|
| /tools/perf/pmu-events/ |
| D | README | 8 The 'jevents' program tries to locate and process JSON files in the directory
11 - Regular files with '.json' extension in the name are assumed to be
12 JSON files, each of which describes a set of PMU events.
17 - Directories are traversed, but all other files are ignored.
30 All the topic JSON files for a CPU model/family should be in a separate
41 Using the JSON files and the mapfile, 'jevents' generates the C source file,
138 files, relative to the directory containing the mapfile.csv
151 i.e the three CPU models use the JSON files (i.e PMU events) listed
|
| D | Build | 14 # Locate/process JSON files in pmu-events/arch/
|
| /tools/memory-model/scripts/ |
| D | README | 23 Run all litmus tests having .litmus.out files from previous
42 in .litmus.out files.
55 and record the results in .litmus.out files.
|
| /tools/testing/selftests/futex/ |
| D | README | 13 directory or purely as header files under include/, I'm leaning toward the
28 implemented in header files, avoiding the need to compile intermediate object
29 files.
|
| /tools/vm/ |
| D | slabinfo-gnuplot.sh | 225 files[$idx]=$p
233 files[$idx]=$p
|
| /tools/testing/selftests/media_tests/ |
| D | regression_test.txt | 22 and cdev user-after-free fixes. This opens media dev files and sits in
34 Start 6 open_loop_test.sh tests with different /dev/mediaX files. When
|
| /tools/build/Documentation/ |
| D | Build.txt | 7 Basically the user provides set of 'Build' files that list objects and
66 To follow the above example, the user provides following 'Build' files:
91 that contain request objects names in Build files.
157 All existing '.cmd' files are included in the Build process to follow properly
|