Searched full:environment (Results 1 – 25 of 1302) sorted by relevance
12345678910>>...53
| /kernel/linux/linux-5.10/include/linux/ |
| 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.
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/ |
| D | ia_css_env.h | 26 * CSS-API host-code by the environment in which the CSS-API code runs.
37 /* Environment with function pointers for local IA memory allocation.
38 * This provides the CSS code with environment specific functionality
47 /* Environment with function pointers to access the CSS hardware. This includes
75 /* Environment with function pointers to print error and debug messages.
84 /* Environment structure. This includes function pointers to access several
85 * features provided by the environment in which the CSS API is used.
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| 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.
|
| /kernel/linux/linux-4.19/tools/perf/Documentation/ |
| 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.
|
| /kernel/linux/linux-4.19/Documentation/filesystems/ |
| D | gfs2-uevents.txt | 18 The ADD uevent has two environment variables: SPECTATOR=[0|1]
26 has the same environment variables as the ADD uevent. The ONLINE
27 uevent, along with the two environment variables for spectator and
40 two environment variables, JID= which specifies the journal id which
48 without checking the environment variables to discover the state, we
70 Information common to all GFS2 uevents (uevent environment variables)
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| 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)
|
| /kernel/linux/linux-4.19/drivers/tee/ |
| D | Kconfig | 1 # Generic Trusted Execution Environment Configuration
3 tristate "Trusted Execution Environment support"
9 Environment (TEE).
|
| /kernel/linux/linux-4.19/security/tomoyo/ |
| 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.
|
| /kernel/linux/linux-5.10/security/tomoyo/ |
| 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.
|
| /kernel/linux/linux-5.10/drivers/tee/ |
| D | Kconfig | 2 # Generic Trusted Execution Environment Configuration
4 tristate "Trusted Execution Environment support"
12 Environment (TEE).
|
| /kernel/liteos_m/ |
| D | README.md | 80 ### Setting Up the Environment
82 …environment for a development board, you must set up the basic system environment for OpenHarmony …
|
| /kernel/linux/linux-4.19/Documentation/kbuild/ |
| D | kconfig.txt | 33 Environment variables for '*config'
37 This environment variable can be used to specify a default kernel config
42 If you set KCONFIG_OVERWRITECONFIG in the environment, Kconfig will not
47 If you set CONFIG_ in the environment, Kconfig will prefix all symbols
52 Environment variables for '{allyes/allmod/allno/rand}config'
59 use the environment variable KCONFIG_ALLCONFIG as a flag or a filename
89 Environment variables for 'randconfig'
125 Environment variables for 'syncconfig'
134 This environment variable can be set to specify the path & name of the
139 This environment variable can be set to specify the path & name of the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/kbuild/ |
| D | kconfig.rst | 37 Environment variables for `*config`
41 This environment variable can be used to specify a default kernel config
46 If you set KCONFIG_OVERWRITECONFIG in the environment, Kconfig will not
51 If you set `CONFIG_` in the environment, Kconfig will prefix all symbols
57 Environment variables for '{allyes/allmod/allno/rand}config'
66 use the environment variable KCONFIG_ALLCONFIG as a flag or a filename
102 Environment variables for 'randconfig'
145 Environment variables for 'syncconfig'
154 This environment variable can be set to specify the path & name of the
159 This environment variable can be set to specify the path & name of the
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| 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
|
| /kernel/linux/linux-5.10/scripts/ |
| D | jobserver-exec | 6 # with PARALLELISM environment variable set, and releases the jobs back again.
17 # Fetch the make environment options.
50 # Any missing environment strings or bad fds should result in just
56 # environment variable and let the child figure out what is best.
|
| /kernel/linux/linux-5.10/tools/testing/selftests/rcutorture/bin/ |
| D | functions.sh | 115 # architecture, unless overridden with the TORTURE_BOOT_IMAGE environment
139 # the kernel at hand. Override with the TORTURE_QEMU_CMD environment variable.
161 # Use TORTURE_QEMU_CMD environment variable or appropriate
170 # and the TORTURE_QEMU_INTERACTIVE environment variable.
192 # and TORTURE_QEMU_INTERACTIVE environment variables.
280 # environment variable is set, in which case the string that is be added is
|
| /kernel/linux/linux-5.10/drivers/misc/echo/ |
| 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
|
| /kernel/linux/linux-4.19/drivers/staging/unisys/Documentation/ |
| D | overview.txt | 22 environment (e.g., block, network, or input), and are collectively referred
73 devices it discovers, as it includes a MODALIAS environment variable of this
74 form in the hotplug uevent environment when each virtual device is
226 (e.g., /sys/block/) in the guest environment for each s-Par virtual device.
257 (e.g., /sys/class/net/) in the guest environment for each s-Par virtual
297 Linux environment by calling input_report_key() and input_report_abs().
301 usyscon Partition Desktop into a Linux environment via the
302 usyscon_partitiondesktop-*.rpm, or into a Windows environment via
304 Linux environment by clicking the console icon in the s-Par web UI.
|
| /kernel/linux/linux-5.10/drivers/staging/unisys/Documentation/ |
| D | overview.txt | 22 Linux guest environment (e.g., block, network, or input), and are collectively
73 devices it discovers, as it includes a MODALIAS environment variable of this
74 form in the hotplug uevent environment when each virtual device is
226 (e.g., /sys/block/) in the guest environment for each s-Par virtual device.
257 (e.g., /sys/class/net/) in the guest environment for each s-Par virtual
297 Linux environment by calling input_report_key() and input_report_abs().
301 usyscon Partition Desktop into a Linux environment via the
302 usyscon_partitiondesktop-*.rpm, or into a Windows environment via
304 Linux environment by clicking the console icon in the s-Par web UI.
|
| /kernel/linux/linux-5.10/Documentation/powerpc/ |
| D | isa-versions.rst | 21 - PowerPC Virtual Environment Architecture Book II v2.02
22 - PowerPC Operating Environment Architecture Book III v2.02
24 - PowerPC Virtual Environment Architecture Book II v2.01
25 - PowerPC Operating Environment Architecture Book III v2.01
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| 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
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | intel_txt.txt | 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
|
| /kernel/linux/linux-5.10/Documentation/staging/ |
| D | tee.rst | 7 A TEE (Trusted Execution Environment) is a trusted OS running in some
8 secure environment, for example, TrustZone on ARM CPUs, or a separate
190 The AMD-TEE driver handles the communication with AMD's TEE environment. The
191 TEE environment is provided by AMD Secure Processor.
195 software-based Trusted Execution Environment (TEE) designed to enable
239 TEE environment.
240 * TEE_CMD_ID_UNLOAD_TA - unloads TA binary from TEE environment.
262 talk to AMD's TEE. AMD's TEE provides a secure environment for loading, opening
|
| /kernel/linux/linux-4.19/drivers/misc/echo/ |
| D | echo.h | 76 - There is no signal being generated within the environment being
96 there is any signal from within the environment being cancelled it may upset
100 and the environment is not, things will be OK. Clearly, it is easy to tell when
101 we are sending a significant signal. Telling, if the environment is generating
105 The key problem in detecting when the environment is sourcing significant
|
12345678910>>...53