| /Zephyr-latest/samples/kernel/metairq_dispatch/src/ |
| D | main.c | 22 } threads[NUM_THREADS]; variable
40 } threads[NUM_THREADS]; member
64 int ret = k_msgq_put(&threads[m.target].msgq, &m, K_NO_WAIT); in metairq_fn()
130 int lidx = stats.threads[t].nevt++; in record_latencies()
132 if (lidx < ARRAY_SIZE(stats.threads[t].latencies)) { in record_latencies()
133 stats.threads[t].latencies[lidx] = latency; in record_latencies()
160 if (stats.threads[i].nevt == 0) { in record_latencies()
165 calc_stats(stats.threads[i].latencies, in record_latencies()
166 stats.threads[i].nevt, in record_latencies()
188 int ret = k_msgq_get(&threads[id].msgq, &m, K_FOREVER); in thread_fn()
[all …]
|
| /Zephyr-latest/kernel/ |
| D | thread_monitor.c | 19 if (thread == _kernel.threads) { in z_thread_monitor_exit()
20 _kernel.threads = _kernel.threads->next_thread; in z_thread_monitor_exit()
24 prev_thread = _kernel.threads; in z_thread_monitor_exit()
55 for (thread = _kernel.threads; thread; thread = thread->next_thread) { in k_thread_foreach()
75 for (thread = _kernel.threads; thread; thread = thread->next_thread) { in k_thread_foreach_unlocked()
107 for (thread = _kernel.threads; thread; thread = thread->next_thread) { in k_thread_foreach_filter_by_cpu()
131 for (thread = _kernel.threads; thread; thread = thread->next_thread) { in k_thread_foreach_unlocked_filter_by_cpu()
|
| D | Kconfig.mem_domain | 46 It's important to note that although supervisor threads can be
61 the architecture supports isolating thread stacks for threads
70 isolated which means threads within the same memory domains
71 have no access to others threads' stacks.
73 If disabled, threads within the same memory domains can access
74 other threads' stacks.
76 Regardless of this settings, threads cannot access the stacks of
77 threads outside of their domains.
|
| /Zephyr-latest/cmake/modules/ |
| D | FindThreads.cmake | 5 # FindThreads module for locating threads implementation.
10 # Indicates if threads are supported.
13 # The threads library to use. Zephyr provides threads implementation and no
17 # Indicates if threads are pthread compatible.
20 # The original implementation tries to find threads library using various
|
| /Zephyr-latest/tests/subsys/debug/coredump_threads/src/ |
| D | main.c | 14 static struct k_thread threads[THREAD_COUNT]; variable
44 &threads[i], in coredump_threads_suite_setup()
58 k_thread_name_set(&threads[i], thread_name); in coredump_threads_suite_setup()
71 k_thread_join(&threads[i], K_FOREVER); in ZTEST()
|
| /Zephyr-latest/samples/subsys/canbus/isotp/ |
| D | Kconfig | 14 int "RX threads stack size"
17 Stack size (in bytes) used for the RX threads.
20 int "RX threads priority"
23 Priority used for the RX threads.
|
| /Zephyr-latest/tests/arch/common/timing/src/ |
| D | main.c | 19 static struct k_thread threads[MAX_NUM_THREADS]; variable
108 k_thread_create(&threads[i], tstack[i], STACK_SIZE, in ZTEST()
111 k_thread_cpu_mask_enable(&threads[i], i); in ZTEST()
112 k_thread_start(&threads[i]); in ZTEST()
116 k_thread_join(&threads[i], K_FOREVER); in ZTEST()
|
| /Zephyr-latest/doc/kernel/services/scheduling/ |
| D | index.rst | 6 The kernel's priority-based scheduler allows an application's threads
41 to be the current thread. When multiple ready threads of the same priority
46 (:kconfig:option:`CONFIG_SCHED_DEADLINE`) and a choice of threads have equal
49 enabled, two threads are only considered to have the same priority when both
57 cooperative threads and preemptive threads.
62 runtime overhead and performance scaling when many threads are added.
67 very fast constant time performance for single threads and very low code size.
69 that will never see more than a small number (3, maybe) of runnable threads in
79 quickly into the many thousands of threads.
81 Use this for applications needing many concurrent runnable threads (> 20 or
[all …]
|
| /Zephyr-latest/tests/benchmarks/sched_userspace/src/ |
| D | main.c | 70 static k_tid_t threads[MAX_NB_THREADS]; variable
87 threads[tid] = k_thread_create(&app_threads[tid].thread, in exec_test()
102 k_thread_start(threads[tid]); in exec_test()
105 k_thread_join(threads[tid], K_FOREVER); in exec_test()
|
| /Zephyr-latest/tests/benchmarks/posix/threads/ |
| D | README.rst | 7 This benchmark creates and joins as many threads as possible within a configurable time window.
8 It provides a rough comparison Zephyr's POSIX threads (pthreads) with Zephyr's kernel threads
21 API, Thread ID, time(s), threads, cores, rate (threads/s/core)
|
| /Zephyr-latest/samples/philosophers/src/ |
| D | main.c | 219 k_thread_create(&threads[i], &stacks[i][0], STACK_SIZE, in start_threads()
226 k_thread_name_set(&threads[i], tname); in start_threads()
228 k_object_access_grant(fork(i), &threads[i]); in start_threads()
229 k_object_access_grant(fork((i + 1) % NUM_PHIL), &threads[i]); in start_threads()
231 k_thread_start(&threads[i]); in start_threads()
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | overview.rst | 9 User mode threads are considered to be untrusted by Zephyr and are therefore
10 isolated from other user mode threads and from the kernel. A flawed or
22 cannot compromise the kernel or other threads.
25 with their own group of threads and private data structures, which are
31 For threads running in a non-privileged CPU state (hereafter referred to as
52 threads in the same memory domain, depending on hardware.
54 - On MPU systems, threads may only access their own stack buffer.
56 - On MMU systems, threads may access any user thread stack in the same
59 - By default, program text and read-only data are accessible to all threads
62 - User threads by default are not granted default access to any memory
[all …]
|
| D | index.rst | 6 Zephyr offers the capability to run threads at a reduced privilege level
10 For details on creating threads that run in user mode, please see
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | xtensa.rst | 15 The kernel allows threads to use the HiFi Audio Engine DSP registers on boards
17 registers by threads and not ISRs.
33 This mode is used when the application has no threads that use the HiFi
44 The behavior is undefined, if two or more threads attempt to use
46 (nor prevent) multiple threads from using these registers.
51 This mode is used when the application has two or more threads that use HiFi
52 registers. When enabled, the kernel automatically allows all threads to use the
|
| /Zephyr-latest/tests/kernel/common/src/ |
| D | timeout_order.c | 36 static struct k_thread threads[NUM_TIMEOUTS]; variable
56 (void)k_thread_create(&threads[ii], stacks[ii], STACKSIZE, in ZTEST()
87 k_thread_join(&threads[ii], K_FOREVER); in ZTEST()
|
| /Zephyr-latest/samples/basic/threads/ |
| D | README.rst | 5 Spawn multiple threads that blink LEDs and print information to the console.
10 This example demonstrates spawning multiple threads using
11 :c:func:`K_THREAD_DEFINE`. It spawns three threads. Each thread is then defined
20 When either of these threads toggles its LED, it also pushes information into a
49 :zephyr-app: samples/basic/threads
|
| /Zephyr-latest/samples/arch/smp/pi/ |
| D | README.rst | 8 This sample application calculates Pi independently in many threads, and
19 number of threads to use (``THREADS_NUM``).
40 Calculate first 240 digits of Pi independently by 16 threads.
46 All 16 threads executed by 4 cores in 28 msec
|
| /Zephyr-latest/doc/kernel/services/synchronization/ |
| D | events.rst | 16 event object is referenced by its memory address. One or more threads may wait
18 event object. When new events are delivered to the event object, all threads
32 conditions of multiple threads waiting on the event object. All threads whose
36 requested events, or for any of them. Furthermore, threads making a wait request
39 threads wait on the same event object.
83 /* notify threads that data is available */
104 /* notify threads that more data is available */
160 Use events to pass small amounts of data to multiple threads at once.
|
| /Zephyr-latest/soc/silabs/silabs_siwx91x/ |
| D | Kconfig.defconfig | 18 # WiseConnect create threads with realtime priority. Default (10kHz) clock tick
19 # prevent proper use of the system with these threads.
|
| /Zephyr-latest/subsys/debug/coredump/ |
| D | Kconfig | 70 threads and all data required to debug threads.
107 Core dump will contain the threads metadata section containing
108 any necessary data to enable debugging threads
111 bool "Dump privilege stack of user threads"
116 Dump the privilege stack of user threads.
|
| /Zephyr-latest/tests/kernel/pending/ |
| D | README.txt | 5 This test verifies that preemptible threads can pend on the following
36 Testing preemptible threads block on fifos ...
39 Testing preemptible threads block on lifos ...
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | fetch_and_get.rst | 31 Using fetch and get sensor can be read in a polling manner from software threads.
47 Triggers may not be set from user mode threads, and the callback is not
61 * Driver dedicated threads have dedicated stack (RAM) which only gets used for
63 * Driver dedicated threads *do* get their own priority typically which lets you
64 prioritize trigger handling among other threads.
65 * Driver dedicated threads will not have head of line blocking if the driver
|
| /Zephyr-latest/tests/subsys/logging/log_immediate/src/ |
| D | log_immediate_test.c | 30 static struct k_thread threads[NUM_THREADS]; variable
64 tids[i] = k_thread_create(&threads[i], stacks[i], STACK_SIZE, in ZTEST()
|
| /Zephyr-latest/tests/benchmarks/sched_queues/ |
| D | Kconfig | 16 int "Number of threads"
19 This option specifies the maximum number of threads that the test
22 differences as the number of threads in the ready queue changes.
|
| /Zephyr-latest/tests/benchmarks/wait_queues/ |
| D | Kconfig | 16 int "Number of threads"
19 This option specifies the maximum number of threads that the test
22 differences as the number of threads in the wait queue changes.
|
