You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7bd9403
Browse filesBrowse the repository at this point in the historyBrowse files
schedule: move zephyr_ll_user.c to src/kernel/schedule
zephyr_ll_user.c creates the memory domain and heap of the user-space
LL scheduler thread and checks the heap pointers passed to the heap
system calls. Despite its name it runs in kernel mode. Move it to
src/kernel/schedule, where it is built into the sof_kernel library.
Update the schedule and user-space READMEs, and stop giving it as an
example of a user-side file. Only Zephyr builds it, for
CONFIG_SOF_USERSPACE_LL. No functional change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
Copy file name to clipboardExpand all lines: src/include/sof/userspace/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ its subdirectories span all tiers.
75
75
| Tier | Meaning | Directories |
76
76
|------|---------|-------------|
77
77
|**Kernel-only**| OS integration, HAL, boot, inter-core. Never executes in a user thread. Must not be reached directly from user code — only via a syscall. |`kernel/` (see [its README](../../../kernel/README.md)), `arch/`, `drivers/`, `platform/`, `trace/` * |
78
-
|**Boundary / bridge**| Owns the syscalls and the thread / memory-domain setup. Split internally: some translation units run kernel-side, some user-side (e.g. `handler-kernel.c` vs `handler-user.c`, `zephyr_ll.c` vs `zephyr_ll_user.c`). |`schedule/`, `ipc/`, `debug/debug_stream/`*, and (in the Zephyr integration tree) `zephyr/syscall/`|
78
+
|**Boundary / bridge**| Owns the syscalls and the thread / memory-domain setup. Split internally: some translation units run kernel-side, some user-side (e.g. `handler-kernel.c` vs `handler-user.c`). |`schedule/`, `ipc/`, `debug/debug_stream/`*, and (in the Zephyr integration tree) `zephyr/syscall/`|
79
79
|**Application**| Audio pipeline / component logic that runs in user threads under userspace configs. |`audio/`|
80
80
|**Shared library**| Context-agnostic code linked into whichever context calls it. Must stay "user-safe": no privileged operations (no direct MMIO, no spinlocks held across syscalls, no raw kernel object access) so it is safe when pulled into a user build. |`math/`, `module/`|
81
81
|**Mixed**| A directory whose files span more than one tier; see its own README for per-file classification. |`lib/`|
@@ -152,7 +152,7 @@ marker at its declaration site.* Conversely, marked data is **user-writable**, s
152
152
must never trust it — re-validate on every use. DP modules running under
153
153
`SOF_USERSPACE_APPLICATION` access data through their per-module memory domain set up by the
154
154
proxy or DP thread infrastructure, not through `APP_TASK_*` / `APP_SYSUSER_*` markers. See
0 commit comments