[DRAFT] userspace LL/audio test PR (latest ver: V35) by kv2019i · Pull Request #10558 · thesofproject/sof

kv2019i · 2026-02-19T17:31:12Z

SOF has recently gained ability to run DP (=preemptable audio tasks) in Zephyr user-space.

This PR is an early stage pull-request for changes to extend this capability to all of the audio pipeline code, and specifically the LL (low-latency) tasks.

This early stage as the design is not set in stone and the PR uses a number of short cuts in order to move (and tests) incrementally larger sets of audio functionality.

kv2019i · 2026-02-19T17:32:45Z

Running the pipeline_two_components_user test added in this PR, on a Intel PTL, looks like this:

START - pipeline_two_components_user
[ 0.000163] <inf> sof_boot_test: pipeline_two_components: copier module_id = 3
[ 0.000163] <inf> sof_boot_test: pipeline_two_components: running test with user memory domain
[ 0.000163] <inf> pipe: pipeline_new: pipeline new pipe_id 2 priority 0
[ 0.000163] <dbg> ipc: ipc4_get_drv: found type 22, uuid 0xa00bc350U
[ 0.000163] <dbg> module_adapter: module_adapter_new_ext: start
[ 0.000163] <dbg> module_adapter: module_adapter_mem_alloc: using ll user heap for module
[ 0.000165] <dbg> module_adapter: module_init: comp:2 0x3 entry
[ 0.000165] <dbg> dma: z_impl_sof_dma_get: dma_get(), dma-probe id = 0
[ 0.000165] <inf> dma: z_impl_sof_dma_get: dma_get() ID 0 sref = 1 busy channels 0
[ 0.000165] <dbg> module_adapter: module_init: comp:2 0x3 done
[ 0.000165] <dbg> module_adapter: module_adapter_new_ext: comp:2 0x3 done
[ 0.000165] <dbg> ipc: ipc4_add_comp_dev: add comp 0x3
[ 0.000165] <dbg> ll_schedule: zephyr_domain_thread_tid: entry
[ 0.000165] <dbg> component: comp_grant_access_to_thread: grant access to mutex 0x400bf798 for thread 0x400bf6c0
[ 0.000165] <dbg> component: comp_grant_access_to_thread: grant access to mutex 0x400bf798 for thread 0x401894e0
[ 0.000165] <inf> sof_boot_test: pipeline_two_components: host copier created, comp_id = 0x3
[ 0.000165] <dbg> ipc: ipc4_get_drv: found type 22, uuid 0xa00bc350U
[ 0.000165] <dbg> module_adapter: module_adapter_new_ext: start
[ 0.000165] <dbg> module_adapter: module_adapter_mem_alloc: using ll user heap for module
[ 0.000165] <dbg> module_adapter: module_init: comp:2 0x10003 entry
[ 0.000165] <inf> copier: copier_dai_init: comp:2 0x10003 dd 0x4019d280 initialized, index -1
[ 0.000165] <dbg> dma: z_impl_sof_dma_get: dma_get(), dma-probe id = 0
[ 0.000165] <inf> dma: z_impl_sof_dma_get: dma_get() ID 0 sref = 1 busy channels 0
[ 0.000165] <inf> ipc: dai_config: comp:2 0x10003 dai type = 3 index = 0 dd 0x4019d280
[ 0.000165] <dbg> ipc: dai_config: comp:2 0x10003 Alloc dai_spec_config 0xa019d480 size size 84
[ 0.000165] <dbg> module_adapter: module_init: comp:2 0x10003 done
[ 0.000165] <dbg> module_adapter: module_adapter_new_ext: comp:2 0x10003 done
[ 0.000165] <dbg> ipc: ipc4_add_comp_dev: add comp 0x10003
[ 0.000165] <dbg> ll_schedule: zephyr_domain_thread_tid: entry
[ 0.000165] <dbg> component: comp_grant_access_to_thread: grant access to mutex 0x400bf7e0 for thread 0x400bf6c0
[ 0.000165] <dbg> component: comp_grant_access_to_thread: grant access to mutex 0x400bf7e0 for thread 0x401894e0
[ 0.000165] <inf> sof_boot_test: pipeline_two_components: DAI copier created, comp_id = 0x10003
[ 0.000166] <dbg> buffer: buffer_alloc: buffer_alloc()
[ 0.000166] <dbg> buffer: buffer_alloc_struct: buffer_alloc_struct()
[ 0.000166] <dbg> userspace_helper: user_grant_dai_access_all: Granted DAI access to thread 0x401894e0 for 45 devices
[ 0.000166] <dbg> userspace_helper: user_grant_dma_access_all: Granted DMA device access: dma@72c00 to thread 0x401894e0
[ 0.000166] <dbg> userspace_helper: user_grant_dma_access_all: Granted DMA device access: dma@72800 to thread 0x401894e0
[ 0.000166] <dbg> userspace_helper: user_grant_dma_access_all: Granted DMA device access: dma@79800 to thread 0x401894e0
[ 0.000166] <dbg> userspace_helper: user_grant_dma_access_all: Granted DMA device access: dma@79400 to thread 0x401894e0
[ 0.000166] <inf> sof_boot_test: pipeline_two_components: user thread started, waiting for completion
[ 0.000170] <dbg> pipe: pipeline_reset: pipe:2 0x3 pipe reset
[ 0.000170] <dbg> pipe: pipeline_comp_reset: pipe:2 0x3 current->comp.id = 0x3, dir = 0
[ 0.000170] <dbg> module_adapter: module_adapter_reset: comp:2 0x3 resetting
[ 0.000170] <dbg> copier: copier_reset: comp:2 0x3 entry
[ 0.000170] <dbg> buffer: comp_buffer_free: buf:0 0x0 buffer_free()
[ 0.000170] <dbg> module_adapter: module_adapter_reset: comp:2 0x3 done
[ 0.000170] <dbg> pipe: pipeline_comp_reset: pipe:2 0x3 current->comp.id = 0x10003, dir = 0
[ 0.000170] <dbg> module_adapter: module_adapter_reset: comp:2 0x10003 resetting
[ 0.000170] <dbg> copier: copier_reset: comp:2 0x10003 entry
[ 0.000170] <dbg> buffer: comp_buffer_free: buf:0 0x0 buffer_free()
[ 0.000170] <dbg> module_adapter: module_adapter_reset: comp:2 0x10003 done
[ 0.000170] <dbg> pipe: pipeline_disconnect: comp:2 0x3 disconnect buffer 0 as sink
[ 0.000170] <dbg> pipe: pipeline_disconnect: comp:2 0x10003 disconnect buffer 0 as source
[ 0.000170] <dbg> buffer: comp_buffer_free: buf:0 0x0 buffer_free()
[ 0.000170] <dbg> buffer: comp_buffer_free: buf:0 0x0 buffer_free()
[ 0.000170] <dbg> module_adapter: module_adapter_reset: comp:2 0x10003 done
[ 0.000170] <dbg> pipe: pipeline_disconnect: comp:2 0x3 disconnect buffer 0 as sink
[ 0.000170] <dbg> pipe: pipeline_disconnect: comp:2 0x10003 disconnect buffer 0 as source
[ 0.000170] <dbg> buffer: comp_buffer_free: buf:0 0x0 buffer_free()
[ 0.000170] <dbg> module_adapter: module_adapter_free: comp:2 0x3 start
[ 0.000170] <inf> dma: z_impl_sof_dma_put: dma_put(), dma = 0x400c8488, sref = 0
[ 0.000170] <dbg> module_adapter: module_adapter_free: comp:2 0x10003 start
[ 0.000170] <inf> dma: z_impl_sof_dma_put: dma_put(), dma = 0x400c8518, sref = 0
[ 0.000170] <dbg> pipe: pipeline_free: pipe:2 0x3 entry
[ 0.000170] <inf> sof_boot_test: pipeline_two_components: two component pipeline test complete
PASS - pipeline_two_components_user in 0.023 seconds

kv2019i · 2026-03-09T17:13:40Z

V2 snapshot pushed:

pipeline_two_components() tests now passes on Intel PTL hardware. a pipeline with two components is created, resources set up, pipeline is run with LL scheduler and then torn down freeing up all resources
introduces change to schedule.h interface to support LL scheduler
multiple limitations still in code (marked with WIP/HACK prefixes): limited to single core, some impact to non-user builds

kv2019i · 2026-03-17T18:30:33Z

V3 snapshot pushed:

added skeleton implementation for user-space IPC handling (only one IPC message type supported for now)
added a test case (ipc4_create_pipeline_check) to test the above

kv2019i · 2026-03-17T18:31:20Z

Test output for the new test added in V3:

[ 0.000063] <inf> ipc: ipc_cmd: rx : 0x110a1800|0x0
[ 0.000063] <dbg> ipc: ipc_user_forward_cmd: IPC: forward cmd 110a1800
[ 0.000063] <dbg> ipc: ipc_user_thread_fn: IPC user wake, mask 1
[ 0.000063] <dbg> ipc: ipc_pipeline_new: ipc: pipeline id = 10
[ 0.000063] <inf> ipc: ipc4_create_pipeline: pipe_desc a00f9f74, instance 10
[ 0.000063] <inf> pipe: pipeline_new: pipeline new pipe_id 10 priority 3
[ 0.000063] <wrn> pipe: pipeline_new: pipeline trace settings cannot be copied
[ 0.000063] <wrn> pipe: pipeline_new: pipeline position reporting not available
[ 0.000063] <inf> ipc: ipc4_create_pipeline: pipeline_new() -> 0xa01ba580
[ 0.000063] <inf> ipc: ipc4_create_pipeline: success
[ 0.000063] <err> ipc_service: ipc_service_release_rx_buffer: Endpoint not registered
[ 0.000063] <wrn> ipc: ipc_platform_complete_cmd: ipc_service_release_rx_buffer() failed: -2
[ 0.000063] <dbg> ipc: ipc_cmd: tx-reply : 0x31000000|0x0
[ 0.000063] <wrn> ipc: ipc_msg_send: Skipping IPC worker schedule. TODO to fix
[ 0.000063] <inf> sof_boot_test: ipc4_create_pipeline_check: ipc_cmd() returned for pipeline id=10
[ 0.000063] <inf> sof_boot_test: ipc4_create_pipeline_check: pipeline verified in IPC comp list
[ 0.000063] <dbg> pipe: pipeline_free: pipe:10 0x0 entry
[ 0.000063] <inf> sof_boot_test: ipc4_create_pipeline_check: ipc4 create pipeline test complete
[ 0.000063] <inf> main: sof_app_main: SOF on intel_adsp
[ 0.000063] <err> ipc_service: ipc_service_get_tx_buffer_size: Endpoint not registered
[ 0.000063] <err> ipc_service: ipc_service_send: Endpoint not registered
[ 0.000063] <err> main: sof_app_main: SOF initialization failed
[ 0.000063] <inf> main: sof_app_main: SOF initialized
===================================================================
PROJECT EXECUTION SUCCESSFUL

kv2019i · 2026-03-17T18:33:59Z

+	/* works? yes */
+	//return 0;
+
+	printk("ipc %p\n", ipc);


Oops, these shouldn't be here. :)

kv2019i · 2026-03-17T18:35:53Z


 	/* create the pipeline */
-	pipe = pipeline_new(NULL, pipe_desc->primary.r.instance_id,
+	pipe = pipeline_new(heap, pipe_desc->primary.r.instance_id,


@lyakh @jsarha @lgirdwood This is where you'd plug in the vregions stuff to pass a separate heap to each pipe (based on topology description of its needs). In this series, as a placeholder, I use the zephyr_ll_user_heap() instead.

right, maybe put a comment there for now to make re-discovery easier

lyakh

last reviewed commit so far "schedule: zephyr_ll: implement thread_init/free domain ops"

lyakh · 2026-03-17T16:37:46Z

+#ifdef CONFIG_SOF_USERSPACE_LL
+void comp_grant_access_to_thread(const struct comp_dev *dev, struct k_thread *th)
+{
+	assert(dev->list_mutex);


description a bit confusing - this is only granting access to a mutex. Also list_mutex is only added to comp_dev in the next commit.

lyakh · 2026-03-18T08:59:18Z

 	}

-	stream_addr = rballoc_align(flags, size, align);
+	stream_addr = sof_heap_alloc(heap, flags, size, align);


the commit, that is mentioned in the commit message, only moved buffer context objects to particular heaps. This commit moves actual data buffers to them too, which is different and (arguably) more risky

lyakh · 2026-03-18T10:44:29Z

 #define HDA_DMA_BUFFER_PERIOD_COUNT	4

-SHARED_DATA struct sof_dma dma[] = {
+APP_TASK_DATA SHARED_DATA struct sof_dma dma[] = {


do I understand correctly, that this kind of userspace access makes that data writable to userspace?

lyakh · 2026-03-18T10:49:20Z

 comp_err(dev, "requested channel %d is busy", hda_chan);
 return -ENODEV;
 	}
-	hd->chan = &hd->dma->chan[channel];


is this also not needed for the legacy mode? Also below

lyakh · 2026-03-18T11:00:24Z

 	uint64_t next_sync;
 	uint64_t period_in_cycles;
 #endif
+	struct k_heap *heap;


wasn't this already referenced in the previous commit?

lyakh · 2026-03-18T11:21:44Z


-	k_spinlock_init(&dd->dai->lock);
+#ifdef CONFIG_SOF_USERSPACE_LL
+	dd->dai->lock = k_object_alloc(K_OBJ_MUTEX);


check for NULL? Possibly in other locations too

lyakh · 2026-03-18T11:24:25Z

 	k_mutex_lock(dai->lock, K_FOREVER);
-	props = dai_get_properties(dai->dev, direction, stream_id);
-	hs_id = props->dma_hs_id;
+	ret = dai_get_properties_copy(dai->dev, direction, stream_id, &props);


I'm guessing this is made a syscall in one of the commits

lyakh · 2026-03-18T11:27:53Z

 mod_heap = &mod_heap_user->heap;
 	} else {
+#ifdef CONFIG_SOF_USERSPACE_LL
+ mod_heap = zephyr_ll_user_heap();


looks good, but this else is entered under multiple conditions, might need to double-check

lyakh · 2026-03-18T11:34:11Z

 	.schedule_task_before	= zephyr_ll_task_schedule_before,
 	.schedule_task_after	= zephyr_ll_task_schedule_after,
-	.schedule_task_free	= zephyr_ll_task_free,
+	.schedule_task_free	= zephyr_ll_task_sched_free,


let's "spend" 3 more characters and make it ..._schedule_free()

lyakh · 2026-03-18T12:01:00Z

- return -ENOMEM;
- }
+ tr_err(&ll_tr, "Failed to allocate thread object for core %d", core);
+ dt->handler = NULL;


duplicate of line 318

lyakh · 2026-03-18T13:07:30Z

+{
+	const struct sof_man_fw_desc *desc = basefw_vendor_get_manifest();
+	const struct sof_man_module *mod;
+	uint32_t i;


int / unsigned int

lyakh · 2026-03-18T13:07:55Z

+	uint32_t i;
+
+	if (!desc)
+ return -1;


lyakh · 2026-03-18T13:08:04Z

+ return (int)i;
+	}
+
+	return -1;


lyakh · 2026-03-18T13:09:01Z

+	union ipc4_connector_node_id node_id;
+	uint32_t dma_buffer_size;
+	uint32_t config_length;
+} __packed __aligned(4);


does __aligned actually make sense in a type definition?

lyakh · 2026-03-18T13:35:48Z

+ pipe_msg.extension.dat = ipc_user->ipc_msg_ext;
+
+ /* Execute pipeline creation in user context */
+ ipc_user->result = ipc_pipeline_new(ipc_user->ipc, (ipc_pipe_new *)&pipe_msg);


that's brave! ;-) I'd put a huge "TODO" here to make sure not to ship this by chance :-)

lyakh · 2026-03-18T13:53:37Z


 	/* create the pipeline */
-	pipe = pipeline_new(NULL, pipe_desc->primary.r.instance_id,
+	pipe = pipeline_new(heap, pipe_desc->primary.r.instance_id,


right, maybe put a comment there for now to make re-discovery easier

kv2019i · 2026-03-27T13:43:41Z

V4 snapshot pushed:

this is a significant milestone as this version allows to set up a full pipeline in user-space and this can be tested at aplay level (tested on Intel PTL with playback PCM0 of upstream sof-ptl-nocodec.tplg topology)
no changes needed to Zephyr or topology
limitations: multiple WIP changes that break other functionality and e.g. IPC implementation is very much in progress

kv2019i · 2026-03-27T13:46:07Z

Example output with V4 patchset:

--cut--
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sofnocodec [sof-nocodec], device 0: Port0 (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: sofnocodec [sof-nocodec], device 1: Port1 (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: sofnocodec [sof-nocodec], device 2: Port2 (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: sofnocodec [sof-nocodec], device 31: Deepbuffer Port0 (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
$ aplay -Dplughw:0,0 -d120 -fdat -traw /dev/zero && echo success
Playing raw data '/dev/zero' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo
success
$
--cut--

kv2019i · 2026-03-30T17:11:36Z

V5 pushed:

start IPC integration with user/kernel split from Ipc user kernel split #10660 partially merged (from @jsarha and @lgirdwood ) -- I tried to merge the full thing but routing all IPC messages to user thread does not work yet, so left the topmost patches out for now
no other changes (and no rebase)

kv2019i · 2026-04-01T13:08:35Z

V6 pushed:

rebase only, no functionality changes
a couple of PRs from "already submitted group" merged to main so removed from this PR
added Add CONFIG_SOF_OS_LINUX_COMPAT_PRIORITY and use it to fix UAOL regression #10672 to the series to make the test pass again with SOF main

kv2019i · 2026-04-01T14:40:19Z

V7 submitted:

added more changes from Ipc user kernel split #10660 , but not yet the change to route all user IPC to user thread. it turns out there are still multiple issues to tackle, so we are better off to incrementally move more IPC types to be processed in user thread (versus moving all in a single commit)
added fix to granting permissions to IPC thread
add new CONFIG_HOST_DMA_IPC_POSITION_UPDATES to drop unused functionality from IPC4 builds

kv2019i · 2026-04-10T11:53:38Z

V8 submitted:

one more IPC routed to user IPC thread (DELETE_PIPELINE)
introduced sys_mutex as a way to replace spinlocks in code that has to work both in kernel and user threads based on build configuration (core changes submitted separately as ipc4: replace fw_reg spinlock with mutex #10693 )
no rebase yet to make the diff to V7 useful

kv2019i · 2026-04-10T12:05:12Z

V9 submitted:

rebase only, no functional change

kv2019i · 2026-04-14T11:24:17Z

V10:

fast-forward update with two commits on top, one a WIP code change to fix a build issue and another to add a overlay file for Intel PTL
code can be now compiled with:

./scripts/xtensa-build-zephyr.py ptl -o app/os_linux_overlay.conf -o app/overlays/ptl/ll_userspace_overlay.conf ptl

at least following test works with upstream sof-ptl-nocodec.tplg (no special Linux/sof-dev dependencies)

aplay -Dplughw:0,0 -d3 -fdat -traw /dev/zero

kv2019i · 2026-04-15T12:00:50Z

V11 pushed:

MOD_CONFIG_GET/SET, MOD_BIND/UNBIND, MOD_INIT/DELETE_INSTANCE moved to user-space (a bit rough code, but functionality at least works)
no rebase (will do that in V12)
UPDATE: with upstream sof-ptl-nocodec.tplg , one needs drivers: dai: make max dai_config blob size configurable zephyrproject-rtos/zephyr#107341 for Zephyr or otherwise copier set_config will fail

kv2019i · 2026-04-15T13:04:50Z

V12 pushed:

rebase-only, no change to functionality
NOTE: like with V11, one needs drivers: dai: make max dai_config blob size configurable zephyrproject-rtos/zephyr#107341 to test with upstream sof-ptl-nocodec.tplg

kv2019i · 2026-08-10T15:21:17Z

V32 update:

rebased on top of latest SOF main
had to temporarily revert [Userspace LL] schedule: dp: call directly instead of a notifier #11063 as it causes userspace LL tests to fail
fixed a regression with chain DMA (fault with HDMI playback when stopping a stream), problem introduced in V30 update and changes in SOF main

cpu_get_id() ultimately reads a privileged special register via arch_proc_id() (e.g. the Xtensa PRID register). When low-atency pipelines run in user-space threads (CONFIG_SOF_USERSPACE_LL), this read is issued from user mode and faults. While many direct usages of cpu_get_id() have been removed from SOF codebase, multiple usages remain. As the remaining usages are mostly on less frequently used code paths (most via cpu_is_me() call, which is used in IPC handling), opt to keep the remaining cpu_get_id() calls and make the function available as a system call. The system call machinery is gated on CONFIG_SOF_FULL_ZEPHYR_APPLICATION so unit-test builds keep the plain inline definition. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

In CONFIG_SOF_USERSPACE_LL builds the LL scheduler thread runs unprivileged, so every Zephyr kernel object it accesses must be explicitly granted to it. In commit ffa52df ("schedule: ll: dynamically allocate the semaphore"), task semaphores were converted to dynamically allocated objects. Only the bootstrap task's semaphore was granted to the LL thread (in zephyr_ll_init_context()); tasks created later (e.g. chain_dma) were not, so pausing/stopping such a task while it was running crashed the DSP. Fix the issue by grant the LL scheduling thread access to the task's semaphore at allocation time, from the syscall implementation which runs in privileged context. The task's LL scheduler is resolved via task->sch (bound in schedule_task_init() using the core-explicit user scheduler list), because zephyr_ll_domain()/cpu_get_id()-based helpers are unreliable in a syscall context: zephyr_ll_domain() reads the kernel scheduler list and returns NULL for the user-space LL scheduler. Add zephyr_domain_thread_tid_for_core() to look up the LL thread for an explicit core without relying on cpu_get_id(). Fixes: ffa52df ("schedule: ll: dynamically allocate the semaphore") Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

kv2019i · 2026-08-11T16:06:53Z

V33 update:

now all commits submitted as separate PRs (and linked to this PR)
aside the alraedy submitted, this branch still has three revert commits left, these need to be solved to make LL-user builds work

kv2019i · 2026-08-12T14:01:26Z

V34 update:

all commits either merged or submitted as separate non-draft PRs!!!
this is potentially the last update of this PR
next steps is to start enabling remaining features (notification IPCs, cold section execute, llext, DP scheduling and multicore). this activity is tracked in [DNM][WiP][PoC] userspace LL scheduling: LLEXT & multicore #10945

Place the pipeline position lookup table in the sysuser memory partition and replace k_spinlock with a dynamically allocated k_mutex when CONFIG_SOF_USERSPACE_LL is enabled. Spinlocks disable interrupts which is a privileged operation unavailable from user-mode threads. The mutex pointer is stored in a separate APP_SYSUSER_BSS variable outside the SHARED_DATA struct so Zephyr's kernel object tracking can recognize it for syscall verification. Move pipeline_posn_init() from task_main_start() to primary_core_init() before platform_init(), so the mutex is allocated before ipc_user_init() grants thread access to it. In pipeline_posn_get(), bypass the sof_get() kernel singleton and access the shared structure directly when running in user-space. Grant the ipc_user_init thread access to the pipeline position mutex via new pipeline_posn_grant_access() helper. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

Use the sof_dma_get_status() wrapper to get DMA status in dai_common_position(). This allows the code to be used from user-space context. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com> (cherry picked from commit ab7f6ce)

Support to run DP scheduler when LL is running in user-space is not yet complete, so disable this feature in the overlay for now. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

module_adapter_free() runs in a user-mode thread in userspace-LL mode and calls mod_free_all(). Unlike mod_free(), mod_free_all() was a plain function, so its internal sof_heap_free() calls on the module heap went through the user-mode syscall verifier, which only permits the LL user heap and K_OOPSes on the module heap. Convert mod_free_all() to a syscall so the objpool/heap cleanup runs in supervisor context, matching mod_free(). Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

Replace the per-pool k_mutex embedded in struct module_resources with a single static K_MUTEX_DEFINE() shared by all module resource pools. This approach to implement locking works both in kernel and userspace SOF builds. When userspace is enabled, the resource API is only ever entered from supervisor context (the z_impl_* syscall bodies), so is it ok to have the lock only accessible from kernel. Lock contention is negligible: resource bookkeeping happens at module setup and teardown, not on the processing path, and the mutex carries priority inheritance for the rare overlap. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

This reverts commit 5350783.

Implement a wrapper for this Zephyr interface so it can be used in generic SOF code. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com> (cherry picked from commit ec22a69)

Replace the per-pool k_mutex embedded in struct module_resources with a single static K_MUTEX_DEFINE() shared by all module resource pools. This approach to implement locking works both in kernel and userspace SOF builds. When userspace is enabled, the resource API is only ever entered from supervisor context (the z_impl_* syscall bodies), so is it ok to have the lock only accessible from kernel. Lock contention is negligible: resource bookkeeping happens at module setup and teardown, not on the processing path, and the mutex carries priority inheritance for the rare overlap. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com> (cherry picked from commit 6b6af15)

Make the options from app/overlays/ptl/ll_userspace_overlay.conf the default for the Intel Panther Lake (ptl) and Wildcat Lake (wcl) build targets, so user-space Low-Latency audio pipelines are enabled without having to pass the overlay explicitly. As noted in the overlay header, once user-space LL is enabled for a target by default the settings belong in the SOF board file directly. For ptl the board already provides the user-space base (USERSPACE, dynamic threads, MMU L2 tables, domain partitions), so only the LL overlay options are added and the conflicting telemetry / cold-store / llext / modules defaults are flipped to match the overlay. wcl had no user-space base at all; since CONFIG_SOF_USERSPACE_LL depends on CONFIG_USERSPACE it would otherwise be silently dropped. Mirror ptl's user-space base into the wcl board file as well so LL actually takes effect there. The ll_userspace_overlay.conf file is kept unchanged; it now re-applies identical values and remains usable by development build scripts. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

kv2019i · 2026-08-13T17:10:22Z

V35 update:

this PR update switches two Intel targets to use userspace LL in the default configuration (to trigger CI tests with userspace-LL enable)
failures are expected on test device that depend on multicore or DP (e.g. nocodec topology tests)
no other changes, all code is already submitted as separate PRs and now just waiting for reviews and testing to complete

kv2019i force-pushed the feat/userspace-ll-wip branch from 9cdb1be to 37b0412Compare March 9, 2026 17:07

kv2019i force-pushed the feat/userspace-ll-wip branch from 37b0412 to 7317b18Compare March 17, 2026 18:29

kv2019i commented Mar 17, 2026
View reviewed changes

lyakh reviewed Mar 18, 2026
View reviewed changes

kv2019i force-pushed the feat/userspace-ll-wip branch from 7317b18 to c029d49Compare March 27, 2026 13:37

kv2019i force-pushed the feat/userspace-ll-wip branch from c029d49 to 9c778e4Compare March 30, 2026 17:09

kv2019i mentioned this pull request Mar 31, 2026
userspace: split ipc files into user and kernel features #10666
Merged

kv2019i force-pushed the feat/userspace-ll-wip branch from 9c778e4 to c4b127fCompare April 1, 2026 13:06

kv2019i force-pushed the feat/userspace-ll-wip branch from c4b127f to ad359d6Compare April 1, 2026 14:36

kv2019i mentioned this pull request Apr 9, 2026
ipc4: replace fw_reg spinlock with mutex #10693
Merged

kv2019i force-pushed the feat/userspace-ll-wip branch from ad359d6 to c7e9a37Compare April 10, 2026 11:48

kv2019i force-pushed the feat/userspace-ll-wip branch from c7e9a37 to 8af1be4Compare April 10, 2026 12:04

kv2019i force-pushed the feat/userspace-ll-wip branch from aa5efe0 to 35a61b6Compare April 15, 2026 11:58

kv2019i force-pushed the feat/userspace-ll-wip branch from 35a61b6 to 214c051Compare April 15, 2026 13:03

This was referenced Aug 10, 2026
[Userspace LL] zephyr: cpu: turn cpu_get_id() into a system call #11079
Open
[Userspace LL] schedule: zephyr_ll: grant LL thread access to per-task semaphores #11080
Open

kv2019i changed the title ~~[DRAFT] userspace LL/audio test PR (latest ver: V31)~~[DRAFT] userspace LL/audio test PR (latest ver: V32)Aug 10, 2026

kv2019i mentioned this pull request Aug 11, 2026
[Userspace LL] audio: pipeline: enable position reporting for user-space pipelines #11083
Open

kv2019i added 2 commits August 11, 2026 16:31

kv2019i mentioned this pull request Aug 11, 2026
[Userspace LL] ipc: ipc4: use the SOF sof_dma_get_status() in dai_common_position() #11084
Open

kv2019i force-pushed the feat/userspace-ll-wip branch from 4832df1 to 3b87697Compare August 11, 2026 16:05

kv2019i changed the title ~~[DRAFT] userspace LL/audio test PR (latest ver: V32)~~[DRAFT] userspace LL/audio test PR (latest ver: V33)Aug 11, 2026

jsarha mentioned this pull request Aug 11, 2026
LL userspace ipc_msg_send() and send_resource_notif() syscalls and related changes #10725
Open

This was referenced Aug 12, 2026
[Userspace LL] app: overlays: ptl: ll_userspace: disable DP scheduler #11085
Open
[Userspace LL] module: generic: make resource locking compatible with user-space builds #11086
Open

kv2019i force-pushed the feat/userspace-ll-wip branch from 3b87697 to 8c45fa2Compare August 12, 2026 13:58

kv2019i changed the title ~~[DRAFT] userspace LL/audio test PR (latest ver: V33)~~[DRAFT] userspace LL/audio test PR (latest ver: V34)Aug 12, 2026

kv2019i added 10 commits August 13, 2026 15:51

app: overlays: ptl: ll_userspace: disable DP scheduler
f8ff776
Support to run DP scheduler when LL is running in user-space is not yet complete, so disable this feature in the overlay for now. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

Revert "module: generic: use a single static lock for module resources"
5cdc2de
This reverts commit 5350783.

posix: rtos: implement K_MUTEX_DEFINE() macro
dd37e93
Implement a wrapper for this Zephyr interface so it can be used in generic SOF code. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com> (cherry picked from commit ec22a69)

(---section submitted PRs STOP)
01b0b02

kv2019i force-pushed the feat/userspace-ll-wip branch from 8c45fa2 to 65f092dCompare August 13, 2026 17:05

kv2019i changed the title ~~[DRAFT] userspace LL/audio test PR (latest ver: V34)~~[DRAFT] userspace LL/audio test PR (latest ver: V35)Aug 13, 2026

Uh oh!

Conversation

kv2019i commented Feb 19, 2026

Uh oh!

kv2019i commented Feb 19, 2026

Uh oh!

kv2019i commented Mar 9, 2026

Uh oh!

kv2019i commented Mar 17, 2026

Uh oh!

kv2019i commented Mar 17, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

lyakh left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kv2019i commented Mar 27, 2026

Uh oh!

kv2019i commented Mar 27, 2026

Uh oh!

kv2019i commented Mar 30, 2026

Uh oh!

kv2019i commented Apr 1, 2026

Uh oh!

kv2019i commented Apr 1, 2026

Uh oh!

kv2019i commented Apr 10, 2026

Uh oh!

kv2019i commented Apr 10, 2026

Uh oh!

kv2019i commented Apr 14, 2026

Uh oh!

kv2019i commented Apr 15, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

kv2019i commented Apr 15, 2026

Uh oh!

kv2019i commented Aug 10, 2026

Uh oh!

kv2019i commented Aug 11, 2026

Uh oh!

kv2019i commented Aug 12, 2026

Uh oh!

kv2019i commented Apr 15, 2026•
edited
Loading