Searched refs:executable (Results 1 – 20 of 20) sorted by relevance
/tools/scripts/ |
D | utilities.mak | 139 # Usage: absolute-executable-path-or-empty = $(call lookup,path) 147 # is-executable 149 # Usage: bool-value = $(call is-executable,path) 154 is-executable = $(call _is-executable-helper,$(shell-sq)) 155 _is-executable-helper = $(shell sh -c $(_is-executable-sh)) 156 _is-executable-sh = $(call shell-sq,test -f $(1) -a -x $(1) && echo y) 158 # get-executable 160 # Usage: absolute-executable-path-or-empty = $(call get-executable,path) 162 # The goal is to get an absolute path for an executable; 168 get-executable = $(if $(1),$(if $(is-absolute),$(_ge-abspath),$(lookup))) [all …]
|
/tools/lib/traceevent/Documentation/ |
D | Makefile | 48 _tmp_tool_path := $(call get-executable,$(ASCIIDOC)) 54 _tmp_tool_path := $(call get-executable,$(XMLTO))
|
/tools/perf/scripts/perl/Perf-Trace-Util/ |
D | README | 11 executable; scripts wishing to do that should 'use Context.pm'. 15 perf executable, you add desciptions of the new functions here. 16 scripting_context is a pointer to the perf data in the perf executable
|
/tools/kvm/kvm_stat/ |
D | Makefile | 11 a2x_path := $(call get-executable,$(A2X))
|
/tools/testing/selftests/bpf/ |
D | test_bpftool_build.sh | 41 find $dir -type f -executable -name bpftool -print -exec false {} + && \
|
/tools/testing/selftests/kvm/lib/x86_64/ |
D | vmx.c | 26 uint64_t executable:1; member 431 pml4e[index[3]].executable = true; in nested_pg_map() 443 pdpe[index[2]].executable = true; in nested_pg_map() 455 pde[index[1]].executable = true; in nested_pg_map() 464 pte[index[0]].executable = true; in nested_pg_map()
|
/tools/perf/ |
D | Makefile.config | 181 ifeq ($(call get-executable,$(FLEX)),) 185 ifeq ($(call get-executable,$(BISON)),) 219 PYTHON2 := $(if $(call get-executable,python2),python2,python) 220 override PYTHON := $(call get-executable-or-default,PYTHON,$(PYTHON2)) 222 $(if $(call get-executable,$(PYTHON)-config),$(PYTHON)-config,python-config) 224 $(call get-executable-or-default,PYTHON_CONFIG,$(PYTHON2_CONFIG)) 783 …msg := $(warning Old version of libbfd/binutils things like PE executable profiling will not be av…
|
/tools/usb/usbip/ |
D | COPYING | 135 under Section 2) in object code or executable form under the terms of 152 received the program in object code or executable form with such 156 making modifications to it. For an executable work, complete source 159 control compilation and installation of the executable. However, as a 163 operating system on which the executable runs, unless that component 164 itself accompanies the executable. 166 If distribution of executable or object code is made by offering
|
/tools/perf/Documentation/ |
D | Makefile | 81 _tmp_tool_path := $(call get-executable,$(ASCIIDOC)) 87 _tmp_tool_path := $(call get-executable,$(XMLTO))
|
D | perf.data-file-format.txt | 78 for a executable file name for a pid. An ELF build id is a unique identifier 79 assigned by the linker to an executable. 452 Define a ELF build ID for a referenced executable.
|
D | perf-trace.txt | 242 - map type is either 'd' for non-executable maps or 'x' for executable maps;
|
D | perf-probe.txt | 100 can also list functions in a user space executable / shared library. 140 Specify path to the executable or shared library file for user
|
D | perf-script-perl.txt | 47 available as calls back into the perf executable (see below).
|
D | perf-top.txt | 255 doesn't uses many executable mmap operations. Work is being planed to solve
|
D | perf-config.txt | 228 Each executable and shared library in modern distributions comes with a
|
D | perf-script-python.txt | 441 available as calls back into the perf executable (see below).
|
D | intel-pt.txt | 258 that does not overlap executable memory maps.
|
/tools/testing/selftests/tc-testing/ |
D | README | 39 The path to the tc executable that will be most commonly tested can be defined 43 If you need to test a different tc executable on the fly, you can do so by 127 -p PATH, --path PATH The full path to the tc executable to use
|
/tools/testing/selftests/android/ion/ |
D | README | 67 These will generate 2 executable: ionapp_export, ionapp_import
|
/tools/memory-model/ |
D | README | 10 short) of the Linux kernel, written in the "cat" language and executable
|