Searched refs:directory (Results 1 – 25 of 49) sorted by relevance
12
/tools/perf/pmu-events/ |
D | README | 2 The contents of this directory allow users to specify PMU events in their 5 The main program in this directory, is the 'jevents', which is built and 8 The 'jevents' program tries to locate and process JSON files in the directory 26 sub directory. Thus for the Silvermont X86 CPU: 89 directory, 'jevents' tries to create an empty mapping file to allow the perf 132 is the pathname to the directory containing the CPU's JSON 133 files, relative to the directory containing the mapfile.csv 147 in the directory 'tools/perf/pmu-events/arch/x86/Silvermont_core'.
|
D | Build | 10 # directory and create tables in pmu-events.c.
|
/tools/build/tests/ex/empty2/ |
D | README | 1 This directory is left intentionally without Build file
|
/tools/testing/selftests/rcutorture/bin/ |
D | kvm-recheck-rcuperf.sh | 30 echo Unreadable results directory: $i
|
D | kvm-recheck-lock.sh | 30 echo Unreadable results directory: $i
|
D | kvm-recheck-rcu.sh | 30 echo Unreadable results directory: $i
|
D | configinit.sh | 54 echo Bad build directory: \"$buildloc\"
|
D | kvm.sh | 289 echo Results directory: $resdir/$ds 427 echo Results directory: $resdir/$ds
|
/tools/scripts/ |
D | Makefile.include | 16 $(if $(OUTDIR),, $(error output directory "$(OUTPUT)" does not exist)) 44 PRINT_DIR = --no-print-directory
|
/tools/testing/selftests/ftrace/ |
D | README | 19 Or you can also run testcases under given directory: 29 * The working directory of the script is <debugfs>/tracing/. 36 * You can add a directory for your testcases under test.d/ if needed.
|
/tools/usb/usbip/ |
D | INSTALL | 20 those values to create a `Makefile' in each directory of the package. 47 1. `cd' to the directory containing the package's source code and type 62 source code directory by typing `make clean'. To also remove the 93 own directory. To do this, you can use GNU `make'. `cd' to the 94 directory where you want the object files and executables to go and run 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 117 In addition, if you use an unusual directory layout you can give 232 Look for the package's source code in directory DIR. Usually 233 `configure' can determine that directory automatically.
|
/tools/testing/ktest/examples/ |
D | README | 1 This directory contains example configs to use ktest for various tasks. 25 include/ - The include directory holds default configs that can be
|
/tools/ |
D | Makefile | 74 $(Q)$(MAKE) --no-print-directory -C perf O=$(PERF_O) subdir= 146 $(Q)$(MAKE) --no-print-directory -C perf O=$(PERF_O) subdir= clean
|
/tools/build/ |
D | Makefile | 31 MAKEFLAGS := --no-print-directory
|
/tools/perf/ |
D | Makefile | 102 …UF=1 -f tests/make REUSE_FEATURES_DUMP=1 MK=Makefile SET_PARALLEL=1 --no-print-directory tarpkg out
|
/tools/testing/selftests/rcutorture/doc/ |
D | initrd.txt | 1 This document describes one way to create the initrd directory hierarchy 19 the initrd directory hierarchy. 21 Here are the commands to create a initrd directory for rcutorture using
|
/tools/perf/Documentation/ |
D | perf-test.txt | 16 also will look for a directory with more tests in the form of scripts.
|
D | perf-data.txt | 28 Triggers the CTF conversion, specify the path of CTF data directory.
|
D | perf-annotate.txt | 91 --symfs=<directory>:: 92 Look for files with symbols relative to this directory.
|
D | perf.txt | 27 Setup buildid cache directory. It has higher priority than
|
D | perf-timechart.txt | 54 --symfs=<directory>:: 55 Look for files with symbols relative to this directory.
|
/tools/lib/api/ |
D | Makefile | 15 MAKEFLAGS += --no-print-directory
|
/tools/lib/subcmd/ |
D | Makefile | 17 MAKEFLAGS += --no-print-directory
|
/tools/testing/selftests/ |
D | Makefile | 98 make -s --no-print-directory -C $$TARGET emit_tests >> $(ALL_SCRIPT); \
|
/tools/power/cpupower/ |
D | Makefile | 30 $(if $(OUTDIR),, $(error output directory "$(OUTPUT)" does not exist))
|
12