Searched refs:threads (Results 151 – 175 of 205) sorted by relevance
123456789
74 # threads declared with K_THREAD_DEFINE()
427 The framework is setting up the environment by creating the requested number of threads469 - :kconfig:option:`CONFIG_ZTRESS_MAX_THREADS` - number of supported threads.470 - :kconfig:option:`CONFIG_ZTRESS_STACK_SIZE` - Stack size of created threads.
128 compiled with multithreading support. This means that different threads can
27 …During this time other threads are not blocked in any way as long as there are enough free blocks …32 Again, other threads are not blocked as long as there are enough free blocks for them.
87 int "Predicted maximum number of threads to return on taskstat list"
153 across context switches to allow multiple threads to perform
53 Print privileged stack usage for user threads.407 for debugger RTOS plugins to determine the state of running threads.
150 ``--chunksize 1`` argument, this ensures we keep feeding threads with work152 a few threads. With dynamic load balancing, if a thread finishes early we keep
36 * CVE-2020-10072: all threads can access all socket file descriptors199 * All threads now are always a member of a memory domain. A new200 memory domain ``k_mem_domain_default`` introduced for initial threads209 thread stacks that will never host user threads. This will conserve memory621 * The kernel stacks are used in network related threads to save memory when917 * :github:`28549` - up_squared: tests/kernel/threads/thread_apis/ failed1082 * :github:`27838` - [Coverity CID :212961] Side effect in assertion in tests/kernel/threads/thread_…1130 * :github:`27592` - threads without name show up as junk names in SystemView1220 * :github:`27202` - tests/kernel/threads/thread_apis failure on lpcxpresso55s16_ns1474 * :github:`26030` - RV32M1_RI5CY: tests/kernel/threads/thread_apis and thread_init fails[all …]
453 with the addition of a new CPU affinity API that can "pin" threads to544 - There is a new CPU affinity API available to "pin" threads to733 * ADC driver APIs are now available to threads running in user mode.872 * MQTT is now available to threads running in user mode.1168 * :github:`15150` - tests/kernel/threads/thread_api: "Double faults" when running code coverage in …1199 * :github:`15044` - ARC: test failure in tests/kernel/threads/thread_apis1205 * :github:`15018` - tests/kernel/threads/no-multithreading: Not booting1316 * :github:`14462` - tests/kernel/threads/no-multithreading/testcase.yam: Not Booting1318 * :github:`14454` - tests/kernel/threads/no-multithreading/: Single/Repeated delay boot banner1515 * :github:`13642` - stack canaries don't work with user mode threads[all …]
178 threads to access the value of ``errno`` without making a system call.226 dynamic lazy FP register stacking in threads.653 * Allow user to select pre-emptive or co-operative RX/TX threads.1053 * :github:`31672` - [Coverity CID :216786] Side effect in assertion in tests/kernel/threads/thread_…1152 * :github:`31262` - tests/kernel/threads/tls/kernel.threads.tls.userspace failing1214 * :github:`30810` - tests: kernel: kernel.threads.armv8m_mpu_stack_guard fails on nrf9160dk1286 * :github:`30393` - kernel.threads.tls.userspace fails with SDK 0.12.0-beta on ARM Cortex-M1288 * :github:`30384` - Scheduler doesn't activate sleeping threads on native_posix1903 * :github:`17893` - dynamic threads don't work on x86 in some configurations1909 * :github:`17023` - userspace: thread indexes are not released when dynamic threads lose all refere…
30 * Same kernel & driver APIs for kernel and user mode threads36 * Stack memory protection from other threads314 * :github:`3628` - implement APIs for dropping threads to unprivileged mode
317 * :github:`9664` - tests/kernel/threads/thread_apis/kernel.threads.user_mode crases on QEMU-x86578 * :github:`8128` - scheduler: threads using k_sleep can be _swap()'d back too early589 * :github:`7966` - Move k_thread_foreach() tests to tests/kernel/threads
196 * Added support for preempting threads while they are performing secure calls in Cortex-M.731 * Enabled running without TX or RX threads. By default, one RX thread and739 of network packets when the data is passed between different network threads.911 * Multiple threads can wait an operation (``pm_device_get_async`` and944 individual threads. It is based on a regularly updated kernel timer,1083 * :github:`35764` - tests: kernel: threads: no multithreading: fails with CONFIG_STACK_SENTINEL=y1567 * :github:`33712` - kernel/poll: no error happened when mutil-threads poll a same event at a same t…1598 * :github:`33551` - tests: SMP: Two threads synchronize failed using mutex or semaphore while both …1760 * :github:`33032` - [Coverity CID :219656] Uninitialized scalar variable in tests/kernel/threads/th…1981 * :github:`32145` - ``kernel threads`` and ``kernel stacks`` deadlock in many scenarios[all …]
76 applications that use only non-preemptible threads, because the kernel
247 int "Maximum number of threads in ztress framework"
202 /* When extensions need not be invoked from user mode threads */205 /* When extensions must be invokable from user mode threads */
43 Make sure the priority is lower than lower layer TX threads to
197 When more threads are using getopt please call getopt_state_get to
7 * Context switch time between preemptive threads using k_yield8 * Context switch time between cooperative threads using k_yield30 above capabilities using various configurations involving user threads:
260 Zephyr ifaces may be accessed from other threads without respecting the binding mutex.361 Bindings may be accessed and modified at random by multiple threads, so modifying or reading from a…
188 stack size for these threads here.
103 A system thread that runs when there are no other threads ready to run.
9 # Some BT threads use co-op priorities to implement critical sections,
213 threads per peripheral. RTIO is much lower cost than that.
