From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Maulik Shah <quic_mkshah@quicinc.com>
Cc: caleb.connolly@linaro.org, stephan@gerhold.net,
swboyd@chromium.org, dianders@chromium.org, robdclark@gmail.com,
nikita@trvn.ru, quic_eberman@quicinc.com,
quic_pkondeti@quicinc.com, quic_lsrao@quicinc.com,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
stable@vger.kernel.org,
Volodymyr Babchuk <volodymyr_babchuk@epam.com>
Subject: Re: [PATCH v2] soc: qcom: cmd-db: Map shared memory as WC, not WB
Date: Sun, 28 Jul 2024 22:58:20 -0500 [thread overview]
Message-ID: <172222551317.175430.12484132433706298927.b4-ty@kernel.org> (raw)
In-Reply-To: <20240718-cmd_db_uncached-v2-1-f6cf53164c90@quicinc.com>
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@kernel.org>
prev parent reply other threads:[~2024-07-29 3:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 6:03 Maulik Shah
2024-07-18 7:38 ` Pavan Kondeti
2024-07-18 7:42 ` Caleb Connolly
2024-07-18 7:55 ` Pavan Kondeti
2024-07-18 8:49 ` Caleb Connolly
2024-07-18 7:41 ` Caleb Connolly
2024-07-24 5:01 ` Pavan Kondeti
2024-07-29 3:58 ` Bjorn Andersson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=172222551317.175430.12484132433706298927.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=Volodymyr_Babchuk@epam.com \
--cc=caleb.connolly@linaro.org \
--cc=dianders@chromium.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita@trvn.ru \
--cc=quic_eberman@quicinc.com \
--cc=quic_lsrao@quicinc.com \
--cc=quic_mkshah@quicinc.com \
--cc=quic_pkondeti@quicinc.com \
--cc=robdclark@gmail.com \
--cc=stable@vger.kernel.org \
--cc=stephan@gerhold.net \
--cc=swboyd@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®