Home
last modified time | relevance | path

Searched refs:threads (Results 76 – 100 of 205) sorted by relevance

123456789

/Zephyr-latest/doc/hardware/peripherals/
Dretained_mem.rst27 different threads can safely call the retained memory functions without
/Zephyr-latest/samples/synchronization/
DREADME.rst11 Two threads (A and B) take turns printing a greeting message to the console,
/Zephyr-latest/tests/benchmarks/thread_metric/
DKconfig24 The cooperative context switching benchmark spawns five (5) threads
69 The preemptive context switching benchmark creates five (5) threads
Dthread_metric_readme.txt21 This test consists of 5 threads created at the same priority that
31 This test consists of 5 threads that each have a unique priority.
32 In this test, all threads except the lowest priority thread are
184 This function lets all other threads of same priority execute
/Zephyr-latest/doc/services/debugging/
Dcoredump.rst34 threads and all data required to debug threads.
254 architecture-specific block, zero or one threads metadata block(s),
329 The threads metadata block contains the byte stream of data necessary
330 for debugging threads.
341 - ``T`` to indicate this is a threads metadata block.
354 - Contains data necessary for debugging threads.
/Zephyr-latest/doc/kernel/usermode/
Dmemory_domain.rst38 threads running in user mode can read ro-data and fetch instructions.
84 Note that user threads have access to the stacks of other user threads in
94 disabled. Regardless of these kconfigs, user threads cannot access
95 the stacks of other user threads outside of their memory domains.
102 directly by user mode. In order to use these system calls, invoking threads
170 user mode has over memory domains is that any user thread's child threads
173 All threads are members of a memory domain, including supervisor threads
175 default domain ``k_mem_domain_default`` which will be assigned to threads if
400 threads assigned to it. Threads are assigned to memory domains with an API
/Zephyr-latest/doc/kernel/services/data_passing/
Dlifos.rst7 last in, first out (LIFO) queue, allowing threads and ISRs
48 Any number of threads may wait on an empty LIFO simultaneously.
88 to send data to one or more consumer threads.
Dfifos.rst7 first in, first out (FIFO) queue, allowing threads and ISRs
48 Any number of threads may wait on an empty FIFO simultaneously.
97 to send data to one or more consumer threads.
Dstacks.rst7 last in, first out (LIFO) queue, allowing threads and ISRs
44 Any number of threads may wait on an empty stack simultaneously.
/Zephyr-latest/samples/boards/arc_secure_services/
DREADME.rst32 * Secure interrupts priority > secure threads priority > normal interrupts
33 priority > normal threads priority.
/Zephyr-latest/arch/posix/
DKconfig19 In bytes, stack size for Zephyr threads meant only for the POSIX
/Zephyr-latest/lib/os/
Dp4wq.c175 k_p4wq_add_thread(q, &pp->threads[i], in static_init()
181 int ret = k_thread_cpu_mask_clear(&pp->threads[i]); in static_init()
DKconfig112 bool "Early initialization of P4WQ threads"
114 Initialize P4WQ threads early so that the P4WQ can be used on devices
/Zephyr-latest/include/zephyr/
Dkernel_structs.h221 struct k_thread *threads; /* singly linked list of ALL threads */ member
/Zephyr-latest/doc/develop/optimizations/
Dfootprint.rst9 Stack sizes of various system threads are specified generously to allow for
/Zephyr-latest/samples/subsys/portability/cmsis_rtos_v1/timer_synchronization/
DREADME.rst4 Use timers and message queues from CMSIS RTOS v1 API to synchronize threads.
/Zephyr-latest/samples/subsys/portability/cmsis_rtos_v2/timer_synchronization/
DREADME.rst4 Use timers and message queues from CMSIS RTOS v2 API to synchronize threads.
/Zephyr-latest/doc/kernel/services/other/
Datomic.rst7 by threads and ISRs in an uninterruptible manner. It is a 32-bit variable on
129 All atomic services APIs can be used by both threads and ISRs.
Dthread_local_storage.rst25 variable. This allows user threads to access the value of ``errno`` without
/Zephyr-latest/samples/subsys/ipc/openamp_rsc_table/
DREADME.rst71 Starting application threads!
120 Starting application threads!
/Zephyr-latest/subsys/debug/
Dthread_info.c47 [THREAD_INFO_OFFSET_K_THREADS] = offsetof(struct z_kernel, threads),
/Zephyr-latest/doc/hardware/porting/
Darch.rst45 handling of fatal error in threads (partly optional).
56 * **User Mode Threads**: for supporting threads in user mode.
179 two types of threads: preemptible and cooperative.
183 * Cooperative threads run at a higher priority than preemptible ones, and
203 threads. For example, referencing invalid memory,
336 #. Run the ``tests/kernel/threads/tls`` to make sure the new code works.
503 APIs, which can host kernel threads running in supervisor mode or
517 stack sizes to support user mode threads. In the absence of definitions
598 supervisor threads. This is not required to catch stack overflow from user
599 threads; :kconfig:option:`CONFIG_USERSPACE` is orthogonal.
[all …]
/Zephyr-latest/samples/philosophers/src/
Dphil_obj_abstract.h160 static struct k_thread threads[NUM_PHIL]; variable
/Zephyr-latest/doc/develop/tools/
Dclion.rst47 :file:`zephyr/samples/basic/threads` or another sample project folder.
149 - Zephyr-threads
197 #. Make sure that **Zephyr-threads** is selected in the configuration switcher and click the bug
/Zephyr-latest/subsys/portability/cmsis_rtos_v2/
Dthread.c519 for (thread = _kernel.threads; thread; thread = thread->next_thread) { in osThreadGetCount()
541 for (thread = _kernel.threads; thread; thread = thread->next_thread) { in osThreadEnumerate()

123456789