Searched full:environment (Results 1 – 25 of 701) sorted by relevance
12345678910>>...29
| /Linux-v5.15/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.
|
| /Linux-v5.15/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.
|
| /Linux-v5.15/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.
|
| /Linux-v5.15/scripts/ |
| 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.
50 # Any missing environment strings or bad fds should result in just
56 # environment variable and let the child figure out what is best.
|
| /Linux-v5.15/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)
|
| /Linux-v5.15/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.
|
| /Linux-v5.15/Documentation/kbuild/ |
| D | kconfig.rst | 37 Environment variables for `*config`
41 This environment variable can be used to specify a default kernel config
47 This environment variable specifies a list of config files which can be used
54 If you set KCONFIG_OVERWRITECONFIG in the environment, Kconfig will not
59 If you set `CONFIG_` in the environment, Kconfig will prefix all symbols
65 Environment variables for '{allyes/allmod/allno/rand}config'
74 use the environment variable KCONFIG_ALLCONFIG as a flag or a filename
110 Environment variables for 'randconfig'
153 Environment variables for 'syncconfig'
162 This environment variable can be set to specify the path & name of the
[all …]
|
| /Linux-v5.15/drivers/tee/ |
| D | Kconfig | 2 # Generic Trusted Execution Environment Configuration
4 tristate "Trusted Execution Environment support"
12 Environment (TEE).
|
| /Linux-v5.15/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
|
| D | sysfs-devices-platform-soc-ipa | 56 environment reachable by the IPA hardware.
65 the modem execution environment. The "rx" is from the
76 the modem execution environment. The "tx" is from the
|
| /Linux-v5.15/tools/testing/selftests/bpf/ |
| D | cgroup_helpers.c | 100 * setup_cgroup_environment() - Setup the cgroup environment
106 * to setup the cgroup environment. If setup is successful, 0 is returned.
129 /* Cleanup existing failed runs, now that the environment is setup */ in setup_cgroup_environment()
195 * cleanup_cgroup_environment() - Cleanup Cgroup Testing Environment
306 fprintf(stderr, "Failed to setup cgroup environment\n"); in cgroup_setup_and_join()
326 * setup_classid_environment() - Setup the cgroupv1 net_cls environment
332 * to setup the cgroup environment. If setup is successful, 0 is returned.
420 * cleanup_classid_environment() - Cleanup the cgroupv1 net_cls environment
|
| /Linux-v5.15/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
|
| /Linux-v5.15/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.
|
| /Linux-v5.15/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
|
| /Linux-v5.15/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
|
| /Linux-v5.15/tools/testing/selftests/rcutorture/bin/ |
| D | functions.sh | 148 # architecture, unless overridden with the TORTURE_BOOT_IMAGE environment
172 # the kernel at hand. Override with the TORTURE_QEMU_CMD environment variable.
194 # Use TORTURE_QEMU_CMD environment variable or appropriate
203 # and the TORTURE_QEMU_INTERACTIVE environment variable.
227 # and TORTURE_QEMU_INTERACTIVE environment variables.
315 # environment variable is set, in which case the string that is be added is
|
| /Linux-v5.15/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
|
| /Linux-v5.15/drivers/tee/amdtee/ |
| D | Kconfig | 2 # AMD-TEE Trusted Execution Environment Configuration
8 This implements AMD's Trusted Execution Environment (TEE) driver.
|
| /Linux-v5.15/drivers/tee/optee/ |
| D | Kconfig | 2 # OP-TEE Trusted Execution Environment Configuration
8 This implements the OP-TEE Trusted Execution Environment (TEE)
|
| /Linux-v5.15/scripts/dummy-tools/ |
| 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
|
| /Linux-v5.15/drivers/s390/net/ |
| D | smsgiucv_app.c | 31 /* SMSG related uevent environment variables */
83 /* setting up environment pointers into buf */ in smsg_app_event_alloc()
89 /* setting up environment: sender, prefix name, and message text */ in smsg_app_event_alloc()
137 /* allocate event list element and its environment */ in smsg_app_callback()
|
| /Linux-v5.15/drivers/misc/mei/ |
| D | Kconfig | 40 tristate "Intel Trusted Execution Environment with ME Interface"
44 MEI Support for Trusted Execution Environment device on Intel SoCs
|
| /Linux-v5.15/tools/testing/ktest/examples/ |
| D | README | 2 The configs still need to be customized for your environment, but it
30 given environment.
|
| /Linux-v5.15/Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,bcm947xx-cfe-partitions.txt | 18 1) Bootloader with Broadcom's CFE (Common Firmware Environment)
26 the same header. To distinguish currently used firmware a CFE's environment
|
| /Linux-v5.15/drivers/staging/media/atomisp/pci/hive_isp_css_include/device_access/ |
| D | device_access.h | 47 * environment. Only if the host environment is modelled as on the target
49 * before the target environment is available. AS we cannot wait for that
|
12345678910>>...29
