Just noticed on my ARM Cortex-R4 build, that when building with CONFIG_USERSPACE enabled, along with CONFIG_INIT_STACKS, the private stacks are not pre-initialized. The user stacks are indeed init'ed

Hi Andrew, I opened GH issue #26912, and Stephanos is assigned to it. My platform is an internal chip, that has an R5 core. I'm fairly certain that one of our team members uses QEMU, though, so I'll c

In v2.3 when building with CONFIG_USERSPACE enabled, I see that we do not do a context switch a short time after POR. I've chased this back and found the the cpus[0].nested has incremented to 6, so th

I'm getting intermittent run-time failures such as: syscall z_hdlr_k_uptime_get failed check: Memory region 0x0002ff70 (size 8) write access denied ***** Hardware exception ***** Current thread ID = 0

I have a work Q that will run in user state and attempting to send work to it. This results in intermittent failures. The issue I see in my current test is that I have taken an interrupt while _curren

I've noticed that on ARM Cortex-R with user mode enabled, that when we enter the system call handlers, such as z_hdlr_k_str_out(), that interrupts are disabled. It seems to me that external interrupts