Home
last modified time | relevance | path

Searched refs:threads (Results 126 – 150 of 205) sorted by relevance

123456789

/Zephyr-latest/tests/lib/mpsc_pbuf/src/
Dmain.c985 static struct k_thread threads[2]; variable
1019 for (int i = 0; i < ARRAY_SIZE(threads); i++) { in start_threads()
1020 tids[i] = k_thread_create(&threads[i], stacks[i], 1024, t_entry, in start_threads()
1028 for (int i = 0; i < ARRAY_SIZE(threads); i++) { in start_threads()
/Zephyr-latest/doc/kernel/usermode/
Dsyscalls.rst5 User threads run with a reduced set of privileges than supervisor threads:
7 limited part of the memory map. System calls (may) allow user threads to
12 Private kernel data should never be made available to user mode threads
380 user threads will never have access to. The implementation functions get passed
422 counter value, and this could be meddled with by user threads that have access
609 the thread object isn't initialized. This is because for threads, the
/Zephyr-latest/boards/native/doc/
Darch_soc.rst107 all threads, kernel, and HW models:
153 an appropriate kernel primitive to synchronize your threads.
186 This is due to how Zephyr allocated threads' stacks are not *actually* being used like they are
409 Zephyr kernel. Whenever the Zephyr kernel desires to context switch two threads, the POSIX arch,
415 Note that all threads use a normal Linux pthread stack, and do not use
/Zephyr-latest/samples/subsys/zbus/remote_mock/
DREADME.rst13 …ests using any language on a computer to talk directly via channels with threads running on a devi…
/Zephyr-latest/doc/hardware/arch/
Darm_cortex_m.rst409 * the mechanism is essential for detecting stack overflows in supervisor threads, or
410 user threads in privileged mode; stack overflows in threads in user mode will always be
413 no memory corruption occurs when supervisor threads overflow their stack memory
498 * an unprivileged RW region for the current thread's stack area (for user threads)
541 threads in and out.
550 and restored in context-switch, if the corresponding threads have
/Zephyr-latest/arch/riscv/
DKconfig.isa44 RISC-V threads running in the same memory space.
/Zephyr-latest/kernel/
Dthread.c593 new_thread->next_thread = _kernel.threads; in z_setup_new_thread()
594 _kernel.threads = new_thread; in z_setup_new_thread()
/Zephyr-latest/doc/connectivity/networking/
Dnet_config_guide.rst254 There several network specific threads in a network enabled system.
255 Some of the threads might depend on a configure option which can be
273 the **kernel threads** command.
/Zephyr-latest/subsys/logging/
DKconfig.processing40 to the logger deadlock if logging is enabled in threads used for
/Zephyr-latest/doc/hardware/peripherals/sensor/
Dread_and_decode.rst58 * All sensor processing can be done in user mode (memory protected) threads.
/Zephyr-latest/tests/bsim/bluetooth/mesh/
DREADME.rst114 the harness, as the previous callbacks are all executed in hardware threads.
/Zephyr-latest/tests/benchmarks/app_kernel/
DREADME.txt10 user/kernel and user/user). However, any configuration involving user threads
/Zephyr-latest/samples/
Dsample_definition_and_criteria.rst57 - ".*Waited and joined with 3 threads"
/Zephyr-latest/samples/subsys/llext/edk/
DREADME.rst21 semaphores, spawning threads to listen for events or simply publishing or
/Zephyr-latest/doc/kernel/services/threads/
Dworkqueue.rst29 starving other threads.
101 A handler function can use any kernel API available to threads. However,
326 * :c:func:`k_work_flush()` may be invoked from threads to block until the work
331 * :c:func:`k_work_cancel_sync()` may be invoked from threads to block until
504 The workqueue API is designed to be safe when invoked from multiple threads
/Zephyr-latest/samples/subsys/zbus/priority_boost/
DREADME.rst122 The developer must enable the priority boost and properly attach all the observers to their threads.
/Zephyr-latest/doc/kernel/memory_management/
Dslabs.rst47 Any number of threads may wait on an empty memory slab simultaneously;
/Zephyr-latest/drivers/ethernet/
DKconfig.stm32_hal56 With pre-emptive threads, the thread can be pre-empted.
/Zephyr-latest/doc/kernel/services/
Dpolling.rst319 Use :c:func:`k_poll` to consolidate multiple threads that would be pending
329 threads, basically when a single thread operates as a main "server" or
Dinterrupts.rst54 Many kernel APIs can be used only by threads, and not by ISRs. In cases
55 where a routine may be invoked by both threads and ISRs the kernel
145 switching between two threads that are using the IRQ lock is
162 Disabling an IRQ prevents *all* threads in the system from being preempted
215 the currently executing cooperative thread or other higher-priority threads
/Zephyr-latest/tests/arch/arm/arm_interrupt/
DREADME.txt22 The second test verifies that threads in user mode, despite being able to call
/Zephyr-latest/samples/boards/renesas/openamp_linux_zephyr/
DREADME.rst170 I: Starting application threads!
/Zephyr-latest/doc/security/
Dsecurity-overview.rst149 assign resources to individual threads or groups of threads. Stack,
207 detecting and trapping stack overruns. Individual threads should
210 - **Thread separation:** Individual threads should only have access to
211 their own memory resources. As threads are scheduled, only memory
/Zephyr-latest/doc/services/portability/posix/overview/
Dindex.rst41 While Zephyr supports running multiple :ref:`threads <threads_v2>` (possibly in an
/Zephyr-latest/doc/releases/
Drelease-notes-1.12.rst45 * kernel/sched: Don't preempt cooperative threads
278 * Enhanced threads test suite
552 * :github:`7020` - tests/kernel/smp: Test fails, scheduler schedules the threads on only one core
664 * :github:`7644` - k_mem_slab_free triggers rescheduling even when no threads are pending
714 * :github:`7754` - tests/kernel/threads/lifecycle/thread_init register corruption on ARM with user …
760 * :github:`8049` - kernel: scheduler tries to make polling threads active
800 * :github:`8214` - Failed test: kernel.threads.customdata_get_set_coop

123456789