[DRAFT/TESTING] userspace LL/audio test PR (latest ver: V43) 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-19T15:41:19Z

V36:

refresh and marking as ready to review to enable more CI coverage for this PR
marking as DNM, no intention to merge this PR

Copilot

Pull request overview

This PR is an early-stage step toward running low-latency (LL) audio pipeline work in Zephyr user-space by making pipeline position tracking safe/accessible from user threads, and by enabling the required Zephyr userspace configuration on ACE30 boards.

Changes:

Move pipeline_posn_init() earlier in the Zephyr init sequence and add user-thread access grants for the pipeline position mutex.
Update pipeline position locking to use a mutex (userspace-safe) when CONFIG_SOF_USERSPACE_LL is enabled, and avoid copying non-userspace-accessible trace context.
Enable/adjust userspace LL-related Kconfig settings in ACE30 PTL/WCL board configs and disable features noted as not yet userspace-compatible.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
zephyr/wrapper.c	Removes late pipeline position init from `task_main_start()` (init is moved earlier).
src/schedule/zephyr_ll.c	Adds warning/handling when task-free semaphore wait times out.
src/ipc/ipc-common.c	Grants IPC userspace thread access to the pipeline position mutex.
src/init/init.c	Calls `pipeline_posn_init()` earlier (before `platform_init()` / userspace IPC init).
src/include/sof/audio/pipeline.h	Declares `pipeline_posn_grant_access()` for userspace LL builds.
src/include/sof/audio/pipeline-trace.h	Adds a build-time guard for userspace LL + non-Zephyr-log trace usage.
src/audio/pipeline/pipeline-graph.c	Uses mutex-based locking for pipeline position offsets under userspace LL and adds access-grant helper.
app/boards/intel_adsp_ace30_wcl.conf	Enables userspace + userspace LL and disables currently incompatible features.
app/boards/intel_adsp_ace30_ptl.conf	Enables userspace LL and disables currently incompatible features.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

+	if (wait_ret && task->state != SOF_TASK_STATE_FREE) {
+		tr_warn(&ll_tr, "task %p still active on free (state %d, semret %d)",
+			task, task->state, wait_ret);
+		zephyr_ll_task_done(sch, task);
+	}


kv2019i · 2026-08-21T15:19:08Z

V37 version:

fix for DSP panics with topologies that use PCH DMIC
fix for memory alloc errors with topologies requiring more than 256KiB of total user-space heap

kv2019i · 2026-08-24T16:05:49Z

V38 update:

updated to include latest version of LL userspace ipc_msg_send() and send_resource_notif() syscalls and related changes #10725
included fix under review at audio: tdfb: place IIR emphasis coefficients in .rodata #11116

kv2019i · 2026-08-25T16:44:47Z

V38b:

just refresh, no code changes

intel-sofci · 2026-08-26T15:04:57Z

PR 10558: test results

Run date: 2026-09-04 14:28 UTC

Tested commit: 2d40017d4bb569dc0cc66861dc4c74069a5a3e71

kv2019i · 2026-08-26T16:37:34Z

V39 update:

rebased to latest main (has multiple user-space related patches merged to main)
included submtited version of [userspace LL] vregion related syscalls #11108 (now in review, from @lyakh )
increased heap memory available to userspace pipelines for Intel WCL and PTL targets (allows to run more complex use-cases on top)

kv2019i · 2026-09-02T09:52:49Z

V40 update:

updated to latest main (and newer Zephyr), now includes merged versions of the Zephyr DAI fixes
multiple SOF PRs merged, now using merged versions
took submitted version of [userspace LL] scheduling: LLEXT, DP & multicore #10945
adapted overlay and Intel ptl/wcl configs to enable previsouly disabled features (llext/modules, dp)

kv2019i · 2026-09-03T08:53:30Z

V41 update:

pulled in two more fixes that are in review (ipc: userspace: don't fault when removing an already-sent IPC message #11157 and llext: userspace: clear cold segment descriptors when sections are ab… #11159 )

kv2019i · 2026-09-03T13:00:25Z

V42 update:

cherry pick of [userspace LL] scheduling: LLEXT, DP & multicore #10945 had a error, DP was left disabled while [userspace LL] scheduling: LLEXT, DP & multicore #10945 should enable it
picked another fix submitted for review zephyr: vregion: stop logging spurious "read access denied" on free p… #11163

Add a check to ensure task state is what is expected after k_sem_take() returns in zephyr_ll_task_free(). This is needed to avoid a rare error hit when running stress tests with chain DMA in user-space LL builds. Issue is hard to reproduce, but similar error signature can be created by passing K_NO_WAIT to k_sem_take() and running a test with chain-dma pipeline. Add defensive code that handles this scenario and prints out a warning when unexpected return occurs. Tested with a custom build with K_NO_WAIT passed to k_sem_take(). Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

z_vrfy_ipc_msg_list_remove() rejected any message that was not currently on ipc->msg_list by failing K_SYSCALL_VERIFY(found), which turns into a kernel oops. But ipc_msg_list_remove() is called from ipc_msg_free() / mod_ipc_msg_free() to drop a message that may or may not still be queued. The common case at stream stop / pipeline delete is freeing a message that has already been sent and dequeued: its list node is self-linked (empty), so it is not "found" and the verifier oopses the LL user thread with: <err> os.z_vrfy_ipc_msg_list_remove: syscall z_vrfy_ipc_msg_list_remove ... failed check: found <err> os.z_fatal_error: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0 Relax the checks to avoid this scenario. If the msg->list is empty, it is safe to call z_impl_ipc_msg_list_remove(). The msg->list pointer itself is already verified with K_SYSCALL_MEMORY_WRITE(). Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

…aths vregion_verify() asserts that the vregion metadata object is NOT accessible to the userspace context. It did this with K_OOPS(!K_SYSCALL_MEMORY_READ(vr, sizeof(*vr))); but K_SYSCALL_MEMORY_READ() emits an "os.vregion_verify: ... Memory region <addr> (size 88) read access denied" error via LOG_ERR precisely when the region is inaccessible - i.e. in the expected, correct case for a kernel-only vregion. Probe the mapping directly with arch_buffer_validate(), which performs the same check without logging, and oops only if the userspace context can actually read the metadata. No functional change to the security check; only the false-positive error logging is removed. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

Replace the bare k_heap pointer in struct pipeline with a mod_alloc_ctx object. The context is created in pipeline_new() and freed symmetrically in pipeline_free(). No vregion is associated with this context yet, so allocation behavior is unchanged: sof_ctx_alloc()/sof_ctx_zalloc()/sof_ctx_free() fall back to the plain heap when the context has no vregion. Update all remaining pipeline->heap consumers, including the pipeline and trigger task allocations in pipeline-schedule.c, to go through the alloc context instead of the heap pointer directly. Signed-off-by: Jyri Sarha <jyri.sarha@linux.intel.com> (cherry picked from commit deac1c8)

Create a per-pipeline vregion in pipeline_new() when the IPC4 pipeline extension payload specifies the required heap size, and attach it to the pipeline's alloc context. LL modules on a pipeline with a vregion use it as their allocation backend via vregion_get(), instead of the driver's default heap, and share the pipeline's mod_alloc_ctx. A use_ppl_alloc flag gates the sharing to LL modules only, so DP modules continue to create their own vregion and alloc context as before. Also the behaviour in the case the where ppl_alloc is not available remains unchanged. module_adapter_mem_free() detects whether a module's alloc belongs to its pipeline and either just releases the vregion reference (ppl_alloc case) or tears down the module's own alloc. Setting of dev->pipeline is moved earlier in module_adapter_new_ext() so that we can still use module_adapter_mem_free() in its error handling. Call vregion_set_interim() for the pipeline vregion in pipeline_complete() to switch the allocator to interim mode after all lifetime allocations are done, and release it in pipeline_free(), warning if the refcount does not reach zero. Signed-off-by: Jyri Sarha <jyri.sarha@linux.intel.com> (cherry picked from commit 6407e81)

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>

The upstream SOF nocodec topologies require more than 32 memory partitions. Bump the max to 64. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

Increase the max limit for memory partitions to allow running SOF with sof-ptl-nocodec.tplg when running all pipelines in user-space. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

kv2019i · 2026-09-04T13:54:39Z

V43 update:

update to SOF main
one WIP fix to increase domain partition count for nocodec tests
cherry pick version of in-review Per pipeline vregions/mod_alloc_ctx #11164

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

kv2019i force-pushed the feat/userspace-ll-wip branch from 37b0412 to 7317b18 Compare 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 c029d49 Compare March 27, 2026 13:37

kv2019i force-pushed the feat/userspace-ll-wip branch from c029d49 to 9c778e4 Compare 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 c4b127f Compare April 1, 2026 13:06

kv2019i force-pushed the feat/userspace-ll-wip branch from c4b127f to ad359d6 Compare 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 c7e9a37 Compare April 10, 2026 11:48

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

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

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

kv2019i requested review from LaurentiuM1234, abonislawski, bardliao, dbaluta, lgirdwood, marcinszkudlinski, pblaszko and tmleman as code owners August 19, 2026 15:39

Copilot AI reviewed Aug 19, 2026

View reviewed changes

Comment thread src/schedule/zephyr_ll.c

Comment on lines +626 to +630

if (wait_ret && task->state != SOF_TASK_STATE_FREE) {

tr_warn(&ll_tr, "task %p still active on free (state %d, semret %d)",

task, task->state, wait_ret);

zephyr_ll_task_done(sch, task);

}

softwarecki mentioned this pull request Aug 28, 2026

[userspace LL] Scheduling part of #10945 #11138

Merged

kv2019i and others added 10 commits September 4, 2026 16:35

(---section submitted PRs START)

948c6f4

(---section submitted PRs STOP)

5429126

app: boards: intel_adsp_ace30: bump max domains to 64

dc0d4a3

The upstream SOF nocodec topologies require more than 32 memory partitions. Bump the max to 64. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

app: overlays: ptl: ll_userspace_overlay: increase memory partitions

2d40017

Increase the max limit for memory partitions to allow running SOF with sof-ptl-nocodec.tplg when running all pipelines in user-space. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

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 19, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

kv2019i commented Apr 15, 2026 •

edited

Loading

intel-sofci commented Aug 26, 2026 •

edited

Loading