Home
last modified time | relevance | path

Searched refs:executable (Results 1 – 25 of 91) sorted by relevance

1234

/linux-6.3-rc2/tools/scripts/
A Dutilities.mak147 # 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))
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;
169 _ge-abspath = $(if $(is-executable),$(1))
171 # get-supplied-or-default-executable
173 # Usage: absolute-executable-path-or-empty = $(call get-executable-or-default,variable,default)
[all …]
/linux-6.3-rc2/Documentation/admin-guide/hw-vuln/
A Dmultihit.rst108 non-executable pages. This forces all iTLB entries to be 4K, and removes
112 as non-executable. If the guest attempts to execute in one of those pages,
113 the page is broken down into 4K pages, which are then marked executable.
120 non-executable in all shadow paging modes.
126 non-executable can be controlled with a module parameter "nx_huge_pages=".
134 non-executable huge pages in Linux kernel KVM module. All huge
135 pages in the EPT are marked as non-executable.
137 broken down into 4K pages, which are then marked executable.
/linux-6.3-rc2/tools/power/cpupower/
A DTODO20 -> Run test executable in a forked process.
24 tested executable.
/linux-6.3-rc2/tools/perf/scripts/perl/Perf-Trace-Util/
A DREADME11 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
/linux-6.3-rc2/tools/testing/selftests/resctrl/
A DREADME23 Build executable file "resctrl_tests" from top level directory of the kernel source:
44 Build executable file "resctrl_tests" from this directory(tools/testing/selftests/resctrl/):
/linux-6.3-rc2/tools/kvm/kvm_stat/
A DMakefile11 a2x_path := $(call get-executable,$(A2X))
/linux-6.3-rc2/tools/testing/selftests/arm64/signal/
A DREADME14 - Each signal testcase is compiled into its own executable: a separate
15 executable is used for each test since many tests complete successfully
/linux-6.3-rc2/tools/perf/
A DMakefile.config205 ifeq ($(call get-executable,$(FLEX)),)
209 ifeq ($(call get-executable,$(BISON)),)
255 PYTHON_AUTO := $(if $(call get-executable,python2-config),python2-config,$(PYTHON_AUTO))
256 PYTHON_AUTO := $(if $(call get-executable,python-config),python-config,$(PYTHON_AUTO))
257 PYTHON_AUTO := $(if $(call get-executable,python3-config),python3-config,$(PYTHON_AUTO))
263 PYTHON_CONFIG_AUTO := $(call get-executable,$(PYTHON)-config)
272 override PYTHON_CONFIG := $(call get-executable-or-default,PYTHON_CONFIG,$(PYTHON_AUTO))
273 override PYTHON := $(call get-executable-or-default,PYTHON,$(subst -config,,$(PYTHON_CONFIG)))
/linux-6.3-rc2/tools/testing/selftests/bpf/
A Dtest_bpftool_build.sh45 find $dir -type f -executable -name bpftool -print -exec false {} + && \
/linux-6.3-rc2/include/linux/
A Dbinfmts.h46 struct file *executable; /* Executable to pass to the interpreter */ member
/linux-6.3-rc2/Documentation/admin-guide/
A Dperf-security.rst112 group to Perf tool executable and limit access to the executable for
127 2. Assign the required capabilities to the Perf tool executable file and
162 configured Perf tool executable that, when executes, passes perf_events
165 In case Perf tool executable can't be assigned required capabilities (e.g.
305 executable with CAP_IPC_LOCK capability.
A Djava.rst35 support for executable Jar files::
399 Set the executable permissions of the binary file, with::
423 added executable Jar file support by Kurt Huwig <kurt@iku-netz.de>
/linux-6.3-rc2/tools/perf/tests/shell/
A Dtest_intel_pt.sh381 /* Get a memory page to store executable code */
391 /* Copy executable code to executable memory page */
/linux-6.3-rc2/fs/
A Dexec.c1287 would_dump(bprm, bprm->executable); in begin_new_exec()
1402 fd_install(retval, bprm->executable); in begin_new_exec()
1403 bprm->executable = NULL; in begin_new_exec()
1500 if (bprm->executable) in free_bprm()
1501 fput(bprm->executable); in free_bprm()
1649 struct file *file = bprm->execfd_creds ? bprm->executable : bprm->file; in bprm_creds_from_file()
1790 if (bprm->executable) { in exec_binprm()
1794 bprm->executable = exec; in exec_binprm()
/linux-6.3-rc2/LICENSES/preferred/
A DLGPL-2.088 a textual and legal sense, the linked executable is a combined work, a
225 it, under Section 2) in object code or executable form under the terms
244 an executable that is a derivative of the Library (because it contains
246 library". The executable is therefore covered by this License. Section 6
285 and, if the work is an executable linked with the Library, with the
288 then relink to produce a modified executable containing the modified
305 For an executable, the required form of the "work that uses the Library"
307 executable from it. However, as a special exception, the source code
310 kernel, and so on) of the operating system on which the executable runs,
311 unless that component itself accompanies the executable.
[all …]
A DLGPL-2.1237 it, under Section 2) in object code or executable form under the terms
256 an executable that is a derivative of the Library (because it contains
258 library". The executable is therefore covered by this License. Section 6
297 and, if the work is an executable linked with the Library, with the
300 then relink to produce a modified executable containing the modified
308 than copying library functions into the executable, and (2) will
325 For an executable, the required form of the "work that uses the Library"
327 executable from it. However, as a special exception, the materials to be
330 kernel, and so on) of the operating system on which the executable runs,
331 unless that component itself accompanies the executable.
[all …]
A DGPL-2.0154 under Section 2) in object code or executable form under the terms of
171 received the program in object code or executable form with such
175 making modifications to it. For an executable work, complete source
178 control compilation and installation of the executable. However, as a
182 operating system on which the executable runs, unless that component
183 itself accompanies the executable.
185 If distribution of executable or object code is made by offering
/linux-6.3-rc2/Documentation/ABI/obsolete/
A Dsysfs-selinux-checkreqprot12 1, it weakens security by allowing mappings to be made executable
/linux-6.3-rc2/scripts/dtc/
A Ddtx_diff302 is not executable.
319 Fallback '${__DTC}' was also not in \${PATH} or is not executable.
/linux-6.3-rc2/tools/perf/Documentation/
A DMakefile78 _tmp_tool_path := $(call get-executable,$(ASCIIDOC))
84 _tmp_tool_path := $(call get-executable,$(XMLTO))
/linux-6.3-rc2/tools/usb/usbip/
A DCOPYING135 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
/linux-6.3-rc2/Documentation/devicetree/bindings/mtd/partitions/
A Dbrcm,trx.txt14 device executable binary (e.g. a kernel) as it's what the CFE bootloader starts
/linux-6.3-rc2/Documentation/filesystems/
A Dromfs.rst113 the file; while bit 4 shows if the file is executable or not. The
115 and world executable if it is; except the character and block devices,
139 using the executable bits for special purposes on the socket and fifo
/linux-6.3-rc2/Documentation/security/
A Dself-protection.rst50 Any areas of the kernel with executable memory must not be writable.
61 writable, data is not executable, and read-only data is neither writable
62 nor executable.
212 Blinding literal values for things like JITs, where the executable
/linux-6.3-rc2/tools/testing/selftests/tc-testing/
A DREADME39 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

Completed in 31 milliseconds

1234