Home
last modified time | relevance | path

Searched full:environment (Results 1 – 25 of 734) sorted by relevance

12345678910>>...30

/Linux-v6.1/Documentation/powerpc/
Disa-versions.rst25 - 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-v6.1/include/linux/
Dpsp-tee.h3 * 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-v6.1/drivers/staging/media/atomisp/pci/
Dia_css_env.h27 * CSS-API host-code by the environment in which the CSS-API code runs.
38 /* Environment with function pointers for local IA memory allocation.
39 * This provides the CSS code with environment specific functionality
48 /* Environment with function pointers to access the CSS hardware. This includes
76 /* Environment with function pointers to print error and debug messages.
85 /* Environment structure. This includes function pointers to access several
86 * features provided by the environment in which the CSS API is used.
/Linux-v6.1/tools/perf/Documentation/
Dandroid.txt4 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-v6.1/scripts/
Djobserver-exec6 # 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-v6.1/Documentation/filesystems/
Dgfs2-uevents.rst22 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-v6.1/security/tomoyo/
Denviron.c11 * 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-v6.1/Documentation/kbuild/
Dkconfig.rst37 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-v6.1/drivers/tee/
DKconfig2 # Generic Trusted Execution Environment Configuration
4 tristate "Trusted Execution Environment support"
12 Environment (TEE).
/Linux-v6.1/Documentation/ABI/testing/
Dsysfs-driver-ppi31 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-v6.1/drivers/misc/echo/
Decho.h64 - 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-v6.1/Documentation/x86/
Dintel_txt.rst15 - 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-v6.1/Documentation/devicetree/bindings/nvmem/
Du-boot,env.yaml7 title: U-Boot environment variables
10 U-Boot uses environment variables to store device parameters and
17 Environment data can be stored on various storage entities, e.g.:
/Linux-v6.1/tools/testing/selftests/rcutorture/bin/
Dfunctions.sh148 # 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-v6.1/Documentation/staging/
Dtee.rst7 A TEE (Trusted Execution Environment) is a trusted OS running in some
8 secure environment, for example, TrustZone on ARM CPUs, or a separate
220 The AMD-TEE driver handles the communication with AMD's TEE environment. The
221 TEE environment is provided by AMD Secure Processor.
225 software-based Trusted Execution Environment (TEE) designed to enable
269 TEE environment.
270 * TEE_CMD_ID_UNLOAD_TA - unloads TA binary from TEE environment.
292 talk to AMD's TEE. AMD's TEE provides a secure environment for loading, opening
/Linux-v6.1/drivers/tee/amdtee/
DKconfig2 # AMD-TEE Trusted Execution Environment Configuration
8 This implements AMD's Trusted Execution Environment (TEE) driver.
/Linux-v6.1/drivers/tee/optee/
DKconfig2 # OP-TEE Trusted Execution Environment Configuration
8 This implements the OP-TEE Trusted Execution Environment (TEE)
/Linux-v6.1/tools/testing/selftests/bpf/
Dcgroup_helpers.c183 * setup_cgroup_environment() - Setup the cgroup environment
189 * to setup the cgroup environment. If setup is successful, 0 is returned.
212 /* Cleanup existing failed runs, now that the environment is setup */ in setup_cgroup_environment()
296 * cleanup_cgroup_environment() - Cleanup Cgroup Testing Environment
425 fprintf(stderr, "Failed to setup cgroup environment\n"); in cgroup_setup_and_join()
445 * setup_classid_environment() - Setup the cgroupv1 net_cls environment
451 * to setup the cgroup environment. If setup is successful, 0 is returned.
539 * cleanup_classid_environment() - Cleanup the cgroupv1 net_cls environment
/Linux-v6.1/arch/x86/boot/compressed/
Defi.c11 * efi_get_type - Given a pointer to boot_params, determine the type of EFI environment.
31 debug_putstr("No EFI environment detected.\n"); in efi_get_type()
107 * environment to the caller, but print them for debugging. in get_kexec_setup_data()
110 debug_putstr("kexec EFI environment missing valid configuration table.\n"); in get_kexec_setup_data()
/Linux-v6.1/scripts/dummy-tools/
Dgcc9 # 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-v6.1/drivers/s390/net/
Dsmsgiucv_app.c31 /* 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-v6.1/tools/testing/ktest/examples/
DREADME2 The configs still need to be customized for your environment, but it
30 given environment.
/Linux-v6.1/Documentation/devicetree/bindings/mtd/partitions/
Du-boot.yaml13 Device configuration is stored as a set of environment variables that are
27 Broadcom stores environment variables inside a U-Boot partition. They
/Linux-v6.1/drivers/misc/mei/
DKconfig40 tristate "Intel Trusted Execution Environment with ME Interface"
44 MEI Support for Trusted Execution Environment device on Intel SoCs
/Linux-v6.1/tools/testing/selftests/powerpc/pmu/sampling_tests/
Dbhrb_no_crash_wo_pmu_test.c16 * environment, say:
47 * using PERF_SAMPLE_BRANCH_STACK. Also for environment in bhrb_no_crash_wo_pmu_test()

12345678910>>...30