| /Zephyr-Core-3.6.0/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
11 malicious user mode thread cannot leak or modify the private data/resources
13 control another user mode thread or the kernel.
15 Example use-cases of Zephyr's user mode features:
32 'user mode') we aim to protect against the following:
41 - A user thread will by default have read/write access to its own stack
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
51 - A user thread may have read/write access to the stacks of other user
[all …]
|
| D | mpu_userspace.rst | 16 During the process of dropping a thread to user mode, the privileged stack
21 During system calls, the user mode thread's access to the system call and the
22 passed-in parameters are all validated. The user mode thread is then elevated
25 thread is set back to user mode and the stack is restored to the user stack.
|
| D | index.rst | 3 User Mode
7 which we call user mode. The current implementation is designed for devices
10 For details on creating threads that run in user mode, please see
|
| /Zephyr-Core-3.6.0/tests/subsys/logging/log_core_additional/src/ |
| D | log_test_user.c | 20 LOG_MODULE_REGISTER(user);
23 * Test cases in this file run in user space to improve test coverage
31 LOG_INF("log from user"); in ZTEST_USER()
32 LOG_INF("log from user %d", d); in ZTEST_USER()
40 /* test log_hexdump_from_user() from user space */
59 /* test log_generic() from user space */
69 /* test log_filter_set from user space */
75 /* test log_panic() from user space */
80 LOG_INF("log from user\n"); in ZTEST_USER()
81 LOG_INF("log from user, level %d\n", d); in ZTEST_USER()
|
| /Zephyr-Core-3.6.0/doc/connectivity/networking/ |
| D | qemu_user_setup.rst | 3 Networking with QEMU User
27 More details about User Networking can be obtained from here:
33 In order to use SLIRP with Zephyr, the user has to set the Kconfig option to
34 enable User Networking.
41 In the default configuration, Zephyr only enables User Networking, and does
46 In general, QEMU User Networking can take in a lot of arguments including,
50 * Information about network to use. This may be valuable if the user does
52 * Tell QEMU to start DHCP server at user-defined IP address.
57 offloads this to the user, and expects that they will provide arguments
59 populated by the user.
[all …]
|
| D | armfvp_user_networking_setup.rst | 3 Networking with Arm FVP User Mode
11 using Arm FVP user mode networking with Zephyr.
16 User mode networking emulates a built-in IP router and DHCP server, and routes
17 TCP and UDP traffic between the guest and host. It uses the user mode socket
27 More details about Arm FVP user mode networking can be obtained from here:
28 https://developer.arm.com/documentation/100964/latest/Introduction-to-Fast-Models/User-mode-network…
30 Using Arm FVP User Mode Networking with Zephyr
33 Arm FVP user mode networking can be enabled in any applications and it doesn't
42 * User mode networking does not support forwarding UDP ports on the host to
|
| /Zephyr-Core-3.6.0/samples/userspace/syscall_perf/ |
| D | README.rst | 7 user thread has to go through a system call compared to a supervisor thread that
14 This application creates a supervisor and a user thread.
16 current thread. The user thread has to go through a system call.
27 User thread: 18012 cycles 748 instructions
29 User thread: 20136 cycles 748 instructions
31 User thread: 18014 cycles 748 instructions
|
| /Zephyr-Core-3.6.0/.github/ISSUE_TEMPLATE/ |
| D | 006_nomination.md | 3 about: Nominate a GitHub user for additional rights on the Zephyr Project
20 Use this template to nominate a GitHub user for the Contributor role with
21 Triage permission level, which allows the user to add reviewers to a pull
26 ## GitHub User
28 Provide the following information about the GitHub user:
37 reviewed by the GitHub user that demonstrate the user's dedication to the
|
| /Zephyr-Core-3.6.0/scripts/release/ |
| D | bug_bash.py | 68 """Return a dict with (key = user, value = score)"""
71 user = p.user.login
72 tally[user] = tally.get(user, 0) + 1
77 """Return a dict with (key = score, value = list<user>) sorted in
81 for user, score in self.get_tally().items():
83 rev_tally[score] = [user]
85 rev_tally[score].append(user)
94 """Return a dict with (key = score, value = user) sorted in
99 for user in users:
103 top_ten.append(tuple([score, user]))
[all …]
|
| /Zephyr-Core-3.6.0/doc/kernel/services/other/ |
| D | float.rst | 62 * non-user: A thread that cannot use any floating point registers
64 * FPU user: A thread that can use the standard floating point registers
66 * SSE user: A thread that can use both the standard floating point registers
72 context switches to ensure the computations performed by each FPU user
73 or SSE user are not impacted by the computations performed by the other users.
146 user on a case-by-case basis. A "lazy save" algorithm is used during context
149 FPU user to a non-user thread, and then back to the original FPU user.
153 current FPU user context is saved in the thread object and the ISR is resumed
165 On the ARCv2 architecture, the kernel treats each thread as a non-user
166 or FPU user and the thread must be tagged by one of the
[all …]
|
| /Zephyr-Core-3.6.0/soc/arm/rpi_pico/rp2/ |
| D | Kconfig.soc | 26 by the board definition, not the user.
32 Should be selected by the board definition, not the user.
38 by the board definition, not the user.
44 by the board definition, not the user.
50 by the board definition, not the user.
|
| /Zephyr-Core-3.6.0/doc/build/dts/ |
| D | zephyr-user-node.rst | 2 .. _dt-zephyr-user:
4 The ``/zephyr,user`` node
7 Zephyr's devicetree scripts handle the ``/zephyr,user`` node as a special case:
14 This node is meant for sample code and user applications. It should not be
20 You can store numeric or array values in ``/zephyr,user`` if you want them to
28 zephyr,user {
54 You can store :ref:`phandles <dt-phandles>` in ``/zephyr,user`` if you want to
63 zephyr,user {
100 The ``/zephyr,user`` node is a convenient place to store application-specific
110 zephyr,user {
|
| /Zephyr-Core-3.6.0/doc/kernel/data_structures/ |
| D | index.rst | 15 indicate what user data is "owned" by that node. Instead, the
17 user-defined struct. Macros are provided to retrieve a user struct
21 allocate node objects because the memory is provided by the user).
26 needed will be provided by the user.
|
| /Zephyr-Core-3.6.0/tests/subsys/zbus/integration/src/ |
| D | channels.c | 13 NULL, /* User data */
23 NULL, /* User data */
32 NULL, /* User data */
41 NULL, /* User data */
50 NULL, /* User data */
59 NULL, /* User data */
|
| /Zephyr-Core-3.6.0/tests/kernel/poll/src/ |
| D | test_poll_fail.c | 16 * @brief Test API k_poll with error number events in user mode
34 * @brief Test API k_poll with error member of events in user mode
50 * @brief Test API k_poll with NULL sem event in user mode
72 * @brief Test API k_poll with NULL signal event in user mode
94 * @brief Test API k_poll with NULL fifo event in user mode
116 * @brief Test API k_poll with NULL message queue event in user mode
139 * @brief Test API k_poll_signal_init with NULL in user mode
155 * @brief Test API k_poll_signal_check with NULL object in user mode
175 * in user mode
199 * in user mode
[all …]
|
| /Zephyr-Core-3.6.0/tests/benchmarks/latency_measure/ |
| D | README.rst | 29 where possible, also test the above capabilities using various configurations involving user
33 * Kernel thread to user thread
34 * User thread to kernel thread
35 * User thread to user thread
98 …isr.resume.different.thread.user - Return from ISR to another thread : …
104 …thread.create.user.from.kernel - Create thread : …
105 …thread.start.user.from.kernel - Start thread : …
106 …thread.suspend.user.from.kernel - Suspend thread : …
107 …thread.resume.user.from.kernel - Resume thread : …
108 …thread.abort.user.from.kernel - Abort thread : …
[all …]
|
| /Zephyr-Core-3.6.0/tests/kernel/threads/dynamic_thread_stack/ |
| D | testcase.yaml | 16 # Permutations of (pool | alloc | user)
24 kernel.threads.dynamic_thread.stack.no_pool.no_alloc.user:
38 kernel.threads.dynamic_thread.stack.no_pool.alloc.user:
52 kernel.threads.dynamic_thread.stack.pool.no_alloc.user:
66 kernel.threads.dynamic_thread.stack.pool.alloc.user:
|
| /Zephyr-Core-3.6.0/boards/arm/twr_kv58f220m/ |
| D | twr_kv58f220m.dts | 43 label = "User LED D4";
47 label = "User LED D3";
51 label = "User LED D2";
55 label = "User LED D1";
62 label = "User SW2";
67 label = "User SW3";
72 label = "User SW4";
77 label = "User SW5";
|
| /Zephyr-Core-3.6.0/boards/arm/waveshare_open103z/ |
| D | waveshare_open103z.dts | 28 label = "User LED1";
32 label = "User LED2";
36 label = "User LED3";
40 label = "User LED4";
47 label = "User button";
52 label = "User joystick ENTER";
57 label = "User joystick RIGHT";
62 label = "User joystick UP";
67 label = "User joystick DOWN";
72 label = "User joystick LEFT";
|
| /Zephyr-Core-3.6.0/boards/riscv/rv32m1_vega/ |
| D | rv32m1_vega.dtsi | 33 label = "User LD1";
37 label = "User LD2";
41 label = "User LD3";
45 label = "User LD4";
53 label = "User PWM LD1";
57 label = "User PWM LD2";
61 label = "User PWM LD3";
68 label = "User SW2";
73 label = "User SW3";
78 label = "User SW4";
[all …]
|
| /Zephyr-Core-3.6.0/subsys/bluetooth/controller/ticker/ |
| D | ticker.c | 67 ticker_timeout_func timeout_func; /* User timeout function */
155 /* User operation data structure for start opcode. Used for passing start
182 /* User operation data structure for update opcode. Used for passing update
216 /* User operation data structure for yield/stop opcode. Used for passing yield/
223 /* User operation data structure for slot_get opcode. Used for passing request
242 /* User operation data structure for priority_set opcode. Used for passing
249 /* User operation top level data structure. Used for passing requests to
253 uint8_t op; /* User operation */
262 } params; /* User operation parameters */
267 /* User data structure for operations
[all …]
|
| /Zephyr-Core-3.6.0/include/zephyr/arch/xtensa/ |
| D | arch_inlines.h | 40 * @brief Read a user register.
42 * @param ur Name of user register.
44 * @return Value of user register.
52 * @brief Write to a user register.
54 * @param ur Name of user register.
55 * @param v Value to be written to user register.
|
| /Zephyr-Core-3.6.0/boards/arm/twr_ke18f/ |
| D | twr_ke18f.dts | 60 label = "User LED D9";
64 label = "User LED D8";
68 label = "User LED D7";
72 label = "User LED D6";
77 label = "User Tricolor LED D5 (Red)";
81 label = "User Tricolor LED D5 (Green)";
85 label = "User Tricolor LED D5 (Blue)";
93 label = "User PWM LED D9";
97 label = "User PWM LED D8";
101 label = "User PWM LED D7";
[all …]
|
| /Zephyr-Core-3.6.0/boards/arm/pan1783/doc/ |
| D | index.rst | 42 `pan1783_evb user guide`_ / `pan1783a_evb user guide`_ / `pan1783a_pa_evb user guide`_
45 The User Guide contains (amongst other things) detailed information about
68 .. _pan1783_evb user guide: https://pideu.panasonic.de/development-hub/pan1783/evaluation_board/use…
69 .. _pan1783a_evb user guide: https://pideu.panasonic.de/development-hub/pan1783a/evaluation_board/u…
70 .. _pan1783a_pa_evb user guide: https://pideu.panasonic.de/development-hub/pan1783a_pa/evaluation_b…
|
| /Zephyr-Core-3.6.0/tests/benchmarks/latency_measure/src/ |
| D | thread_switch_yield.c | 13 * When user threads are supported, there are four cases to consider. These are
15 * 2. User thread -> User thread
16 * 3. Kernel thread -> User thread
17 * 4. User thread -> Kernel thread
161 /* User -> User */ in thread_switch_yield()
165 /* Kernel -> User */ in thread_switch_yield()
169 /* User -> Kernel */ in thread_switch_yield()
|
