From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Sibi Sankar <quic_sibis@quicinc.com>,
andersson@kernel.org, krzysztof.kozlowski+dt@linaro.org,
manivannan.sadhasivam@linaro.org
Cc: agross@kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, konrad.dybcio@somainline.org,
amit.pundir@linaro.org, regressions@leemhuis.info,
sumit.semwal@linaro.org, will@kernel.org,
catalin.marinas@arm.com, robin.murphy@arm.com
Subject: Re: [PATCH V3 02/10] dt-bindings: remoteproc: qcom,msm8996-mss-pil: Update memory region
Date: Thu, 12 Jan 2023 10:18:05 +0100 [thread overview]
Message-ID: <c548f9c8-81ac-5d34-c169-420c45c987e2@linaro.org> (raw)
In-Reply-To: <20230111114337.24782-3-quic_sibis@quicinc.com>
On 11/01/2023 12:43, Sibi Sankar wrote:
> The dynamic memory region used for metadata authentication would still
> be a part of the kernel mapping and any access to this region by the
> application processor after assigning it to the remote Q6 will result
> in a XPU violation. This is fixed by using a no-map carveout instead.
> Update the bindings to reflect the addition of the new modem metadata
> carveout on MSM8996 (and similar) SoCs.
>
> Signed-off-by: Sibi Sankar <quic_sibis@quicinc.com>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-01-12 9:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 11:43 [PATCH V3 00/10] Fix XPU violation during modem metadata authentication Sibi Sankar
2023-01-11 11:43 ` [PATCH V3 01/10] dt-bindings: remoteproc: qcom,q6v5: Move MSM8996 to schema Sibi Sankar
2023-01-11 11:43 ` [PATCH V3 02/10] dt-bindings: remoteproc: qcom,msm8996-mss-pil: Update memory region Sibi Sankar
2023-01-12 9:18 ` Krzysztof Kozlowski [this message]
2023-01-11 11:43 ` [PATCH V3 03/10] dt-bindings: remoteproc: qcom,sc7180-mss-pil: Update memory-region Sibi Sankar
2023-01-11 13:29 ` Rob Herring
2023-01-12 20:17 ` Rob Herring
2023-01-12 20:19 ` Rob Herring
2023-01-11 11:43 ` [PATCH V3 04/10] dt-bindings: remoteproc: qcom,sc7280-mss-pil: " Sibi Sankar
2023-01-11 13:29 ` Rob Herring
2023-01-11 11:43 ` [PATCH V3 05/10] remoteproc: qcom_q6v5_mss: Use a carveout to authenticate modem headers Sibi Sankar
2023-01-11 11:54 ` Manivannan Sadhasivam
2023-01-11 12:28 ` Sibi Sankar
2023-01-11 17:40 ` Manivannan Sadhasivam
2023-01-11 11:43 ` [PATCH V3 06/10] arm64: dts: qcom: msm8996: Add a carveout for modem metadata Sibi Sankar
2023-01-11 11:43 ` [PATCH V3 07/10] arm64: dts: qcom: msm8998: " Sibi Sankar
2023-01-11 11:43 ` [PATCH V3 08/10] arm64: dts: qcom: sdm845: " Sibi Sankar
2023-01-11 11:43 ` [PATCH V3 09/10] arm64: dts: qcom: sc7180: " Sibi Sankar
2023-01-11 11:43 ` [PATCH V3 10/10] arm64: dts: qcom: sc7280: " Sibi Sankar
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=c548f9c8-81ac-5d34-c169-420c45c987e2@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=amit.pundir@linaro.org \
--cc=andersson@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_sibis@quicinc.com \
--cc=regressions@leemhuis.info \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sumit.semwal@linaro.org \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).