Home
last modified time | relevance | path

Searched refs:directory (Results 1 – 25 of 49) sorted by relevance

12

/tools/perf/pmu-events/
DREADME2 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'.
DBuild10 # directory and create tables in pmu-events.c.
/tools/build/tests/ex/empty2/
DREADME1 This directory is left intentionally without Build file
/tools/testing/selftests/rcutorture/bin/
Dkvm-recheck-rcuperf.sh30 echo Unreadable results directory: $i
Dkvm-recheck-lock.sh30 echo Unreadable results directory: $i
Dkvm-recheck-rcu.sh30 echo Unreadable results directory: $i
Dconfiginit.sh54 echo Bad build directory: \"$buildloc\"
Dkvm.sh289 echo Results directory: $resdir/$ds
427 echo Results directory: $resdir/$ds
/tools/scripts/
DMakefile.include16 $(if $(OUTDIR),, $(error output directory "$(OUTPUT)" does not exist))
44 PRINT_DIR = --no-print-directory
/tools/testing/selftests/ftrace/
DREADME19 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/
DINSTALL20 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/
DREADME1 This directory contains example configs to use ktest for various tasks.
25 include/ - The include directory holds default configs that can be
/tools/
DMakefile74 $(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/
DMakefile31 MAKEFLAGS := --no-print-directory
/tools/perf/
DMakefile102 …UF=1 -f tests/make REUSE_FEATURES_DUMP=1 MK=Makefile SET_PARALLEL=1 --no-print-directory tarpkg out
/tools/testing/selftests/rcutorture/doc/
Dinitrd.txt1 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/
Dperf-test.txt16 also will look for a directory with more tests in the form of scripts.
Dperf-data.txt28 Triggers the CTF conversion, specify the path of CTF data directory.
Dperf-annotate.txt91 --symfs=<directory>::
92 Look for files with symbols relative to this directory.
Dperf.txt27 Setup buildid cache directory. It has higher priority than
Dperf-timechart.txt54 --symfs=<directory>::
55 Look for files with symbols relative to this directory.
/tools/lib/api/
DMakefile15 MAKEFLAGS += --no-print-directory
/tools/lib/subcmd/
DMakefile17 MAKEFLAGS += --no-print-directory
/tools/testing/selftests/
DMakefile98 make -s --no-print-directory -C $$TARGET emit_tests >> $(ALL_SCRIPT); \
/tools/power/cpupower/
DMakefile30 $(if $(OUTDIR),, $(error output directory "$(OUTPUT)" does not exist))

12