Home
last modified time | relevance | path

Searched full:world (Results 1 – 25 of 537) sorted by relevance

12345678910>>...22

/linux-6.12.1/lib/
Dtest_objagg.c29 struct world { struct
46 static struct objagg_obj *world_obj_get(struct world *world, in world_obj_get() argument
60 if (!world->key_refs[key_id_index(key_id)]) { in world_obj_get()
61 world->objagg_objs[key_id_index(key_id)] = objagg_obj; in world_obj_get()
62 } else if (world->objagg_objs[key_id_index(key_id)] != objagg_obj) { in world_obj_get()
68 world->key_refs[key_id_index(key_id)]++; in world_obj_get()
76 static void world_obj_put(struct world *world, struct objagg *objagg, in world_obj_put() argument
81 if (!world->key_refs[key_id_index(key_id)]) in world_obj_put()
83 objagg_obj = world->objagg_objs[key_id_index(key_id)]; in world_obj_put()
85 world->key_refs[key_id_index(key_id)]--; in world_obj_put()
[all …]
Dtest_module.c3 * This module emits "Hello, world" on printk when loaded.
19 pr_warn("Hello, world\n"); in test_module_init()
/linux-6.12.1/drivers/tee/optee/
Doptee_smc.h75 * Used by non-secure world to figure out which Trusted OS is installed.
88 * Used by non-secure world to figure out which version of the Trusted OS
140 * When calling these functions, normal world has a few responsibilities:
193 * world.
238 * Exchanges capabilities between normal world and secure world
242 * a1 bitfield of normal world capabilities OPTEE_SMC_NSEC_CAP_*
248 * a1 bitfield of secure world capabilities OPTEE_SMC_SEC_CAP_*
249 * a2 The maximum secure world notification number
257 * a0 OPTEE_SMC_RETURN_ENOTAVAIL, can't use the capabilities from normal world
258 * a1 bitfield of secure world capabilities OPTEE_SMC_SEC_CAP_*
[all …]
Doptee_ffa.h7 * This file is exported by OP-TEE and is kept in sync between secure world
8 * and normal world drivers. We're using ARM FF-A 1.0 specification.
17 * Normal world sends requests with FFA_MSG_SEND_DIRECT_REQ and
53 * Used by non-secure world to figure out which version of the Trusted OS
69 * Exchange capabilities between normal world and secure world.
84 * w5: Bitfield of secure world capabilities OPTEE_FFA_SEC_CAP_* below,
85 * w6: The maximum secure world notification number
89 * Secure world supports giving an offset into the argument shared memory
116 * Inform OP-TEE that the normal world is able to receive asynchronous
158 * RPC interrupt return (RPC from secure world). Register usage:
Doptee_msg.h13 * with an instance of OP-TEE running in secure world.
17 * 2. Requests from normal world
110 * Secure and normal world communicates pointers as physical address
111 * instead of the virtual address. This is because secure and normal world
112 * have completely independent memory mapping. Normal world can even have a
115 * structure to secure world.
155 * Value parameters are passed unchecked between normal and secure world.
235 * Part 2 - requests from normal world
275 * Used by non-secure world to figure out which Trusted OS is installed.
290 * Used by non-secure world to figure out which version of the Trusted OS
[all …]
Dffa_abi.c22 * This file implement the FF-A ABI used when communicating with secure world
27 * 3. Low level support functions to register shared memory in secure world
29 * 5. Do a normal scheduled call into secure world
37 * This handle is then used when communicating with secure world.
264 * 3. Low level support functions to register shared memory in secure world
418 * 5. Do a normal scheduled call into secure world
421 * call into secure world. During this call may normal world request help
422 * from normal world using RPCs, Remote Procedure Calls. This includes
562 * Out of threads in secure world, wait for a thread in optee_ffa_yielding_call()
596 * We're done with our thread in secure world, if there's any in optee_ffa_yielding_call()
[all …]
Doptee_private.h39 * This value should be larger than the number threads in secure world to
40 * meet the need from secure world. The number of threads in secure world
134 * @sec_caps: secure world capabilities defined by
156 * OP-TEE in secure world
174 * @do_call_with_arg: enters OP-TEE in secure world
180 * secure world.
199 * world
Dsmc_abi.c38 * This file implement the SMC ABI used when communicating with secure world
42 * 2. Low level support functions to register shared memory in secure world
44 * 4. Do a normal scheduled call into secure world
267 * 2. Low level support functions to register shared memory in secure world
269 * Functions to enable/disable shared memory caching in secure world, that
286 /* We need to retry until secure world isn't busy. */ in optee_enable_shm_cache()
311 /* We need to retry until secure world isn't busy. */ in __optee_disable_shm_cache()
583 * when dynamic shared memory is supported by secure world.
640 * 4. Do a normal scheduled call into secure world
643 * call into secure world. During this call may normal world request help
[all …]
Doptee_rpc_cmd.h31 * Notification from/to secure world.
33 * If secure world needs to wait for something, for instance a mutex, it
34 * does a notification wait request instead of spinning in secure world.
36 * world mutex with a thread waiting thread is unlocked.
Dcall.c33 * needed RPC parameter count reported by secure world
50 * the secure world to tell us when we're out of thread and have to in optee_cq_init()
66 * We're preparing to make a call to secure world. In case we can't in optee_cq_wait_init()
67 * allocate a thread in secure world we'll end up waiting in in optee_cq_wait_init()
70 * Normally if there's no contention in secure world the call will in optee_cq_wait_init()
77 * guarantees that we don't lose a completion if secure world in optee_cq_wait_init()
156 * We're done with the call to secure world. The thread in secure in optee_cq_wait_final()
157 * world that was used for this call is now available for some in optee_cq_wait_final()
172 * was just done with its call to secure world. Since yet another in optee_cq_wait_final()
173 * thread now is available in secure world wake up another eventual in optee_cq_wait_final()
/linux-6.12.1/Documentation/devicetree/bindings/arm/
Dsecure.txt1 * ARM Secure world bindings
6 world or the Secure world. However some devicetree consumers are
13 The general principle of the naming scheme for Secure world bindings
14 is that any property that needs a different value in the Secure world
19 world value is the same as specified for the Normal world by the
30 world consumers (like kernels that run entirely in Secure) to simply
31 describe the view of Secure world using the standard bindings. These
33 world views need to be described in a single device tree.
35 Valid Secure world properties
39 in the secure world. The combination of this with "status" allows
[all …]
/linux-6.12.1/Documentation/devicetree/bindings/iio/
Dmount-matrix.txt13 that produce three-dimensional data in relation to the world where it is
41 external world, the environment where the device is deployed. Usually the data
43 to this world. When using the mounting matrix, the sensor and device orientation
45 world.
47 Device-to-world examples for some three-dimensional sensor types:
49 - Accelerometers have their world frame of reference toward the center of
53 this point. Up and down in the world relative to the device frame of
93 - Magnetometers (compasses) have their world frame of reference relative to the
94 geomagnetic field. The system orientation vis-a-vis the world is defined with
160 space, relative to the device or world point of reference.
/linux-6.12.1/scripts/kconfig/tests/preprocess/builtin_func/
Dexpected_stderr1 Kconfig:8: hello world 1
2 Kconfig:18: hello world 3
3 Kconfig:22: hello world 4
DKconfig4 $(info,hello world 0)
8 $(warning-if,y,hello world 1)
18 $(warning,$(shell,echo hello world 3))
/linux-6.12.1/Documentation/tee/
Dop-tee.rst36 User space Kernel Secure world
56 RPC (Remote Procedure Call) are requests from secure world to kernel driver
74 There are two kinds of notifications that secure world can use to make
75 normal world aware of some event.
84 this is only usable when secure world is entered with a yielding call via
86 world interrupt handlers.
95 special meaning. When this value is received it means that normal world is
98 building block for OP-TEE OS in secure world to implement the top half and
/linux-6.12.1/drivers/scsi/qla2xxx/
Dtcm_qla2xxx.h20 /* Binary World Wide unique Node Name for remote FC Initiator Nport */
58 /* Binary World Wide unique Port Name for FC Target Lport */
60 /* Binary World Wide unique Port Name for FC NPIV Target Lport */
62 /* Binary World Wide unique Node Name for FC NPIV Target Lport */
/linux-6.12.1/Documentation/kbuild/
Dkconfig-macro-language.rst181 For example, $(shell echo hello, world) runs the command "echo hello, world".
182 Likewise, $(info hello, world) prints "hello, world" to stdout. You could say
188 $(shell, echo hello, world)
194 $(shell, echo hello$(comma) world)
/linux-6.12.1/drivers/firmware/arm_ffa/
DKconfig11 the Secure world and Normal world. It also leverages the
/linux-6.12.1/drivers/net/wireless/ath/
Dregd.c29 * This is a set of common rules used by our world regulatory domains.
30 * We have 12 world regulatory domains. To save space we consolidate
35 /* Only these channels all allow active scan on all world regulatory domains */
202 (regd == WORLD)); in is_wwr_sku()
519 * a world regulatory domain and the scheduler hasn't yet processed in ath_reg_notifier_apply()
529 * If common->reg_world_copy is world roaming it means we *were* in ath_reg_notifier_apply()
530 * world roaming... so we now have to restore that data. in ath_reg_notifier_apply()
656 * it's our own custom world regulatory domain, similar to in ath_regd_init_wiphy()
673 * default Atheros world regulatory domain.
/linux-6.12.1/samples/kdb/
Dkdb_hello.c26 kdb_printf("Hello world!\n"); in kdb_hello_cmd()
35 .help = "Say Hello World or Hello [string]",
/linux-6.12.1/tools/testing/selftests/net/af_unix/
Dmsg_oob.c414 sendpair("world", 5, 0); in TEST_F()
426 recvpair("world", 5, 5, 0); in TEST_F()
437 sendpair("world", 5, 0); in TEST_F()
445 recvpair("world", 5, 10, 0); /* Drop OOB and recv() the next skb. */ in TEST_F()
591 sendpair("world", 5, MSG_OOB); in TEST_F()
644 sendpair("world", 5, 0); in TEST_F()
659 recvpair("world", 5, 6, 0); /* TCP recv()s "oworld", ... "o" ??? */ in TEST_F()
748 sendpair("world", 5, MSG_OOB); in TEST_F()
/linux-6.12.1/drivers/firmware/
Dstratix10-svc.c29 * from the secure world for FPGA manager to reuse, or to free the buffer(s)
70 * at secure world.
196 * svc_thread_cmd_data_claim() - claim back buffer from the secure world
201 * Claim back the submitted buffers from the secure world and pass buffer
233 pr_debug("%s: secure world busy, polling again\n", in svc_thread_cmd_data_claim()
247 * Check whether the secure firmware at secure world has finished the FPGA
672 * secure world.
684 /* SMC or HVC call to get shared memory info from secure world */ in svc_normal_to_secure_shm_thread()
732 "timeout to get sh-memory paras from secure world\n"); in svc_get_sh_memory()
738 "failed to get shared memory info from secure world\n"); in svc_get_sh_memory()
[all …]
/linux-6.12.1/include/linux/firmware/intel/
Dstratix10-smc.h14 * service layer driver in normal world (EL1) to communicate with secure
102 * to secure world.
151 * Sync call used by service driver at EL1 to inform secure world that all
152 * data are sent, to check whether or not the secure world had completed
429 * Sync call to check if the secure world have completed service request
/linux-6.12.1/Documentation/admin-guide/sysctl/
Dfs.rst180 in world writable sticky directories, unless they are owned by the
192 time-of-check-time-of-use race, most commonly seen in world-writable
218 don't own in world writable sticky directories, unless they are
228 time-of-check-time-of-use race, most commonly seen in world-writable
238 a sticky world-writable directory, or when the uid of the symlink and
/linux-6.12.1/tools/testing/selftests/bpf/prog_tests/
Dvarlen.c19 const char str2[] = "World!"; in test_varlen()
20 const char exp_str[] = "Hello, \0World!\0"; in test_varlen()

12345678910>>...22