| /linux/tools/net/sunrpc/xdrgen/generators/ |
| H A D | program.py | 6 from jinja2 import Environment
13 environment: Environment, program: str, version: _RpcVersion argument
16 template = environment.get_template("definition/open.j2")
19 template = environment.get_template("definition/procedure.j2")
29 template = environment.get_template("definition/close.j2")
34 environment: Environment, program: str, version: _RpcVersion argument
43 template = environment.get_template("declaration/argument.j2")
53 template = environment.get_template("declaration/result.j2")
59 environment: Environment, program: str, version: _RpcVersion argument
67 template = environment.get_template("decoder/argument.j2")
[all …]
|
| H A D | header_bottom.py | 19 self.environment = create_jinja2_environment(language, "header_bottom")
24 template = get_jinja2_template(self.environment, "declaration", "header")
29 template = get_jinja2_template(self.environment, "definition", "header")
|
| H A D | header_top.py | 19 self.environment = create_jinja2_environment(language, "header_top")
24 template = get_jinja2_template(self.environment, "declaration", "header")
35 template = get_jinja2_template(self.environment, "definition", "header")
|
| H A D | constant.py | 14 self.environment = create_jinja2_environment(language, "constants")
19 template = self.environment.get_template("definition.j2")
|
| H A D | source_top.py | 19 self.environment = create_jinja2_environment(language, "source_top")
25 template = self.environment.get_template(self.peer + ".j2")
|
| /linux/Documentation/kbuild/ |
| H A D | kconfig.rst | 39 Environment variables
42 Environment variables for ``*config``:
45 This environment variable can be used to specify a default kernel config
49 This environment variable specifies a list of config files which can be
55 If you set KCONFIG_OVERWRITECONFIG in the environment, Kconfig will not
59 This environment variable makes Kconfig warn about all unrecognized
66 If you set ``CONFIG_`` in the environment, Kconfig will prefix all symbols
70 Environment variables for ``{allyes/allmod/allno/rand}config``:
74 use the environment variable KCONFIG_ALLCONFIG as a flag or a filename
108 Environment variables for ``randconfig``:
[all …]
|
| /linux/Documentation/arch/powerpc/ |
| H A D | isa-versions.rst | 25 - PowerPC Virtual Environment Architecture Book II v2.02
26 - PowerPC Operating Environment Architecture Book III v2.02
28 - PowerPC Virtual Environment Architecture Book II v2.01
29 - PowerPC Operating Environment Architecture Book III v2.01
32 - PowerPC Virtual Environment Architecture Book II v2.01
33 - PowerPC Operating Environment Architecture Book III v2.01
35 - PowerPC Virtual Environment Architecture Book II v2.00
36 - PowerPC Operating Environment Architecture Book III v2.00
|
| /linux/include/linux/ |
| H A D | psp-tee.h | 3 * AMD Trusted Execution Environment (TEE) interface
17 /* This file defines the Trusted Execution Environment (TEE) interface commands
25 * TEE environment
26 * @TEE_CMD_ID_UNLOAD_TA: Unload TA binary from TEE environment
45 * psp_tee_process_cmd() - Process command in Trusted Execution Environment
53 * TEE environment and waits for a response or until the command times out.
|
| /linux/tools/perf/Documentation/ |
| H A D | android.txt | 4 I. Set the Android NDK environment
13 2. Set cross-compiling environment variables for NDK toolchain and sysroot.
28 Set the environment for the target you want using:
33 NDK sysroot environment variable.
42 3. Set the NDK toolchain environment variable.
68 IV. Environment settings for running perf
70 Some perf features need environment variables to run properly.
|
| /linux/Documentation/tee/ |
| H A D | amd-tee.rst | 4 AMD-TEE (AMD's Trusted Execution Environment)
7 The AMD-TEE driver handles the communication with AMD's TEE environment. The
8 TEE environment is provided by AMD Secure Processor.
12 software-based Trusted Execution Environment (TEE) designed to enable
56 TEE environment.
57 * TEE_CMD_ID_UNLOAD_TA - unloads TA binary from TEE environment.
79 talk to AMD's TEE. AMD's TEE provides a secure environment for loading, opening
|
| H A D | tee.rst | 4 TEE (Trusted Execution Environment)
12 A TEE is a trusted OS running in some secure environment, for example,
|
| /linux/Documentation/filesystems/ |
| H A D | gfs2-uevents.rst | 22 The ADD uevent has two environment variables: SPECTATOR=[0|1]
31 has the same environment variables as the ADD uevent. The ONLINE
32 uevent, along with the two environment variables for spectator and
46 two environment variables, JID= which specifies the journal id which
54 without checking the environment variables to discover the state, we
78 Information common to all GFS2 uevents (uevent environment variables)
|
| /linux/scripts/ |
| H A D | jobserver-exec | 6 # with PARALLELISM environment variable set, and releases the jobs back again.
13 # Extract and prepare jobserver file descriptors from environment.
17 # Fetch the make environment options.
61 # Any missing environment strings or bad fds should result in just
67 # environment variable and let the child figure out what is best.
|
| /linux/Documentation/userspace-api/ |
| H A D | check_exec.rst | 16 environment, and whether the kernel can check if a script is trustworthy or
21 sandboxed and then should not be able to harm the user's environment.
49 execution environment to ensure that direct file execution (e.g.
52 trustworthy according to the caller's environment.
54 In a secure environment, libraries and any executable dependencies should also
57 For such secure execution environment to make sense, only trusted code should
82 environment variables as long as it is not a way to disable the securebits
|
| /linux/security/tomoyo/ |
| H A D | environ.c | 11 * tomoyo_check_env_acl - Check permission for environment variable's name.
28 * tomoyo_audit_env_log - Audit environment variable name log.
41 * tomoyo_env_perm - Check permission for environment variable's name.
44 * @env: The name of environment variable.
112 * tomoyo_write_misc - Update environment variable list.
|
| /linux/drivers/tee/ |
| H A D | Kconfig | 2 # Generic Trusted Execution Environment Configuration
4 tristate "Trusted Execution Environment support"
12 Environment (TEE).
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-ppi | 31 executed in the pre-OS environment. It is the only input from
32 the OS to the pre-OS environment. The request should be an
60 operation to be executed in the pre-OS environment by the BIOS
71 operation to be executed in the pre-OS environment by the BIOS
|
| /linux/Documentation/arch/x86/ |
| H A D | intel_txt.rst | 15 - Measurement and verification of launched environment
112 tboot then verifies certain aspects of the environment (e.g. TPM NV
119 in the TXT environment, it is necessary to create a small VT-x
169 - Tboot will clean up the environment and disable TXT, then use the
174 measured environment upon resume. Once the TXT environment
182 and once the measured environment has been re-established, tboot
|
| /linux/drivers/misc/echo/ |
| H A D | echo.h | 64 - There is no signal being generated within the environment being
84 there is any signal from within the environment being cancelled it may upset
88 and the environment is not, things will be OK. Clearly, it is easy to tell when
89 we are sending a significant signal. Telling, if the environment is generating
93 The key problem in detecting when the environment is sourcing significant
|
| /linux/tools/testing/selftests/rcutorture/bin/ |
| H A D | functions.sh | 148 # architecture, unless overridden with the TORTURE_BOOT_IMAGE environment
175 # the kernel at hand. Override with the TORTURE_QEMU_CMD environment variable.
200 # Use TORTURE_QEMU_CMD environment variable or appropriate
209 # and the TORTURE_QEMU_INTERACTIVE environment variable.
233 # and TORTURE_QEMU_INTERACTIVE environment variables.
321 # environment variable is set, in which case the string that is be added is
|
| /linux/drivers/tee/amdtee/ |
| H A D | Kconfig | 2 # AMD-TEE Trusted Execution Environment Configuration
8 This implements AMD's Trusted Execution Environment (TEE) driver.
|
| /linux/Documentation/devicetree/bindings/nvmem/layouts/ |
| H A D | u-boot,env.yaml | 7 title: U-Boot environment variables layout
10 U-Boot uses environment variables to store device parameters and
17 Environment data can be stored on various storage entities, e.g.:
|
| /linux/arch/x86/boot/compressed/ |
| H A D | efi.c | 13 * efi_get_type - Given a pointer to boot_params, determine the type of EFI environment.
33 debug_putstr("No EFI environment detected.\n"); in efi_get_type()
109 * environment to the caller, but print them for debugging. in get_kexec_setup_data()
112 debug_putstr("kexec EFI environment missing valid configuration table.\n"); in get_kexec_setup_data()
|
| /linux/drivers/nvmem/layouts/ |
| H A D | Kconfig | 30 tristate "U-Boot environment variables layout"
34 U-Boot stores its setup as environment variables. This driver adds
|
| /linux/scripts/dummy-tools/ |
| H A D | gcc | 9 # build environment (typically this happens when you package the kernel for
11 # CONFIG options than the real build environment. So, you probably want to make
13 # super-set of CONFIG options that cover any build environment. If some of the
|