| /Zephyr-latest/samples/subsys/portability/cmsis_rtos_v2/philosophers/src/ |
| D | main.c | 71 static K_THREAD_STACK_ARRAY_DEFINE(stacks, NUM_PHIL, STACK_SIZE);
75 .stack_mem = &stacks[0][0],
81 .stack_mem = &stacks[1][0],
87 .stack_mem = &stacks[2][0],
93 .stack_mem = &stacks[3][0],
99 .stack_mem = &stacks[4][0],
105 .stack_mem = &stacks[5][0],
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | mpu_userspace.rst | 7 set of stacks. These stacks exist in a 1:1 relationship with each thread stack
8 defined in the system. The privileged stacks are created as a part of the
13 stacks, a lookup table, and a set of helper functions are created and added
|
| D | mpu_stack_objects.rst | 9 Thread stacks are declared statically with :c:macro:`K_THREAD_STACK_DEFINE()`.
12 stacks are physically contiguous allocations. This contiguous allocation
13 has implications for the placement of stacks in memory, as well as the
39 constraints are used to place the stacks properly.
|
| D | overview.rst | 44 - A user thread will never by default have access to user thread stacks
47 - A user thread will never by default have access to thread stacks owned
48 by a supervisor thread, or thread stacks used to handle system call
51 - A user thread may have read/write access to the stacks of other user
147 drivers and threads stacks are also considered kernel objects. This ensures
167 - Thread stacks are defined in such a way that exceeding the specified stack
174 All kernel objects, thread stacks, and device driver instances must be defined
|
| /Zephyr-latest/include/zephyr/linker/ |
| D | kobject-priv-stacks.ld | 23 #include <zephyr/linker-kobject-prebuilt-priv-stacks.h>
31 #include <zephyr/linker-kobject-prebuilt-priv-stacks.h>
46 for privileged stacks."
|
| D | common-noinit.ld | 28 #include "kobject-priv-stacks.ld"
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.mem_domain | 61 the architecture supports isolating thread stacks for threads
69 If enabled, thread stacks within the same memory domains are
71 have no access to others threads' stacks.
74 other threads' stacks.
76 Regardless of this settings, threads cannot access the stacks of
|
| D | Kconfig.obj_core | 93 bool "Integrate stacks into object core framework"
96 When enabled, this option integrates stacks into the object core
|
| /Zephyr-latest/tests/subsys/logging/log_immediate/src/ |
| D | log_immediate_test.c | 29 K_THREAD_STACK_ARRAY_DEFINE(stacks, NUM_THREADS, STACK_SIZE);
64 tids[i] = k_thread_create(&threads[i], stacks[i], STACK_SIZE, in ZTEST()
|
| /Zephyr-latest/include/zephyr/sys/ |
| D | p4wq.h | 96 struct z_thread_stack_element *stacks; member
123 .stacks = &(_p4stacks_##name[0][0]), \
162 .stacks = &(_p4stacks_##name[0][0]), \
|
| /Zephyr-latest/tests/kernel/common/src/ |
| D | timeout_order.c | 35 static K_THREAD_STACK_ARRAY_DEFINE(stacks, NUM_TIMEOUTS, STACKSIZE);
56 (void)k_thread_create(&threads[ii], stacks[ii], STACKSIZE, in ZTEST()
|
| D | errno.c | 25 static K_THREAD_STACK_ARRAY_DEFINE(stacks, N_THREADS, STACK_SIZE);
86 k_thread_create(&threads[ii], stacks[ii], STACK_SIZE, in ZTEST()
|
| /Zephyr-latest/subsys/shell/modules/kernel_service/thread/ |
| D | CMakeLists.txt | 16 zephyr_sources_ifdef(CONFIG_KERNEL_THREAD_SHELL_STACKS stacks.c)
|
| D | stacks.c | 91 KERNEL_THREAD_CMD_ADD(stacks, NULL, "List threads stack usage.", cmd_kernel_thread_stacks);
|
| D | Kconfig | 31 Internal helper macro to compile the `stacks` subcommand
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | index.rst | 8 operation of the stacks and how they were implemented.
|
| /Zephyr-latest/arch/arm/core/cortex_a_r/ |
| D | CMakeLists.txt | 11 stacks.c
|
| /Zephyr-latest/boards/qemu/x86/ |
| D | qemu_x86_atom_virt_defconfig | 24 # For now, the mapped stacks require physical addresses
|
| /Zephyr-latest/arch/x86/core/ |
| D | Kconfig.intel64 | 30 so they are typically smaller than the ISR stacks.
64 The more nesting allowed, the more room is required for IRQ stacks.
|
| /Zephyr-latest/samples/philosophers/src/ |
| D | main.c | 219 k_thread_create(&threads[i], &stacks[i][0], STACK_SIZE, in start_threads()
|
| D | phil_obj_abstract.h | 159 static K_THREAD_STACK_ARRAY_DEFINE(stacks, NUM_PHIL, STACK_SIZE);
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | arch.rst | 85 * Switch stacks from MSP to PSP on Cortex-M.
500 Two types of thread stacks exist:
502 - "kernel" stacks defined with :c:macro:`K_KERNEL_STACK_DEFINE()` and related
506 reserved for privilege elevation stacks.
508 - "thread" stacks which typically use more memory, but are capable of hosting
509 thread running in user mode, as well as any use-cases for kernel stacks.
511 If :kconfig:option:`CONFIG_USERSPACE` is not enabled, "thread" and "kernel" stacks are
567 At present, Zephyr does not support stacks that grow upward.
646 Guard carve-outs for kernel stacks are uncommon and should be avoided if
651 This is the case when privilege elevation stacks are not inside the stack
[all …]
|
| /Zephyr-latest/subsys/testsuite/ztest/src/ |
| D | ztress.c | 48 K_THREAD_STACK_ARRAY_DEFINE(stacks, CONFIG_ZTRESS_MAX_THREADS, CONFIG_ZTRESS_STACK_SIZE);
366 tids[i] = k_thread_create(&threads[i], stacks[i], CONFIG_ZTRESS_STACK_SIZE, in ztress_execute()
|
| /Zephyr-latest/samples/net/sockets/dumb_http_server_mt/src/ |
| D | response_big.html.bin | 31 …. Enhancements in security, device management capabilities, connectivity stacks and file systems c…
|
| /Zephyr-latest/samples/net/sockets/dumb_http_server/src/ |
| D | response_big.html.bin | 31 …. Enhancements in security, device management capabilities, connectivity stacks and file systems c…
|
