Re: [PATCH] arm64: dts: qcom: shikra: Mark RPM message RAM as no-memory-wc

From: Vishnu Santhosh

Date: Fri Nov 20 2026 - 04:37:40 EST



On 18-11-2026 06:25 pm, Mukesh Ojha wrote:
On Wed, Nov 18, 2026 at 04:35:55PM +0530, Vishnu Santhosh wrote:
On 17-11-2026 09:49 pm, Mukesh Ojha wrote:
On Tue, Nov 17, 2026 at 01:35:50PM +0530, Vishnu Santhosh wrote:
The RPM message RAM is shared with other subsystems, and parts of it
are not accessible to the APSS. It is expected to be mapped as Device
memory.

The "mmio-sram" compatible makes the SRAM driver map the region as
write-combined (Normal Non-cacheable) memory instead, which allows
speculative reads into the protected parts and results in XPU
violations.

Add no-memory-wc so the region is mapped as Device memory.

Fixes: 66664b5701da ("arm64: dts: qcom: Introduce Shikra SoC base dtsi")
Signed-off-by: Vishnu Santhosh <vishnu.santhosh@xxxxxxxxxxxxxxxx>
Why only for Shikra ?
This XPU violation was seen only on Shikra, and only with Linux
running at EL2 (KVM). It is not seen on Shikra when Linux runs at
EL1 under Gunyah. So, I kept the change to Shikra.
Thats not explained in this commit, why this issue not seen under
Gunyah ?

Under Gunyah, Linux runs at EL1 and Gunyah maps this region as Device
memory at stage-2. The stricter stage-2 type applies, so the
write-combined mapping from the SRAM driver has no effect.

With KVM, Linux runs at EL2 (VHE) and there is no stage-2, so the
write-combined mapping takes effect and speculative reads reach the
protected regions.

The region is expected to be mapped non-write-combined regardless of
the exception level, so I kept the commit message to that. I can add
the EL2 detail in v2 if you prefer.

Vishnu