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

From: Mukesh Ojha

Date: Wed Nov 18 2026 - 07:55:52 EST


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 ?


--
-Mukesh Ojha