[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <172222551317.175430.12484132433706298927.b4-ty@kernel.org>
Date: Sun, 28 Jul 2024 22:58:20 -0500
From: Bjorn Andersson <andersson@...nel.org>
To: Konrad Dybcio <konrad.dybcio@...aro.org>,
Maulik Shah <quic_mkshah@...cinc.com>
Cc: caleb.connolly@...aro.org,
stephan@...hold.net,
swboyd@...omium.org,
dianders@...omium.org,
robdclark@...il.com,
nikita@...n.ru,
quic_eberman@...cinc.com,
quic_pkondeti@...cinc.com,
quic_lsrao@...cinc.com,
linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org,
Volodymyr Babchuk <Volodymyr_Babchuk@...m.com>,
stable@...r.kernel.org,
Volodymyr Babchuk <volodymyr_babchuk@...m.com>
Subject: Re: [PATCH v2] soc: qcom: cmd-db: Map shared memory as WC, not WB
On Thu, 18 Jul 2024 11:33:23 +0530, Maulik Shah wrote:
> Linux does not write into cmd-db region. This region of memory is write
> protected by XPU. XPU may sometime falsely detect clean cache eviction
> as "write" into the write protected region leading to secure interrupt
> which causes an endless loop somewhere in Trust Zone.
>
> The only reason it is working right now is because Qualcomm Hypervisor
> maps the same region as Non-Cacheable memory in Stage 2 translation
> tables. The issue manifests if we want to use another hypervisor (like
> Xen or KVM), which does not know anything about those specific mappings.
>
> [...]
Applied, thanks!
[1/1] soc: qcom: cmd-db: Map shared memory as WC, not WB
commit: f9bb896eab221618927ae6a2f1d566567999839d
Best regards,
--
Bjorn Andersson <andersson@...nel.org>
Powered by blists - more mailing lists