From: Konrad Dybcio <konradybcio@kernel.org>
To: Luca Weiss <luca.weiss@fairphone.com>,
Konrad Dybcio <konradybcio@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
cros-qcom-dts-watchers@chromium.org
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Konrad Dybcio <quic_kdybcio@quicinc.com>
Subject: Re: [RFC PATCH 00/11] Affirm SMMU coherent pagetable walker capability on RPMh SoCs
Date: Thu, 19 Sep 2024 12:07:29 +0200 [thread overview]
Message-ID: <2fb16b35-e6c5-4239-a745-a9dd7412539a@kernel.org> (raw)
In-Reply-To: <D4A2FKPTXHS5.3AHU7ZEKFVMGG@fairphone.com>
On 19.09.2024 9:00 AM, Luca Weiss wrote:
> On Thu Sep 19, 2024 at 12:57 AM CEST, Konrad Dybcio wrote:
>> I only read back the SMMU config on X1E & 7280, but I have it on good
>> authority that this concerns all RPMh SoCs. Sending as RFC just in case.
>>
>> Lacking coherency can hurt performance, but claiming coherency where it's
>> absent would lead to a kaboom.
>
> Hi Konrad!
>
> You want people with the affected SoCs to test this I imagine?
Yeah, would be nice to confirm
>
> Just boot it and see if it doesn't implode, or do you have any more
> elaborate test plan for this?
No, booting should be enough of a test
Konrad
next prev parent reply other threads:[~2024-09-19 10:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 22:57 [RFC PATCH 00/11] Affirm SMMU coherent pagetable walker capability on RPMh SoCs Konrad Dybcio
2024-09-18 22:57 ` [PATCH RFC 01/11] arm64: dts: qcom: qdu1000: Affirm IDR0.CCTW on apps_smmu Konrad Dybcio
2024-09-18 22:57 ` [PATCH RFC 02/11] arm64: dts: qcom: sc7180: " Konrad Dybcio
2024-09-20 13:44 ` Doug Anderson
2024-09-18 22:57 ` [PATCH RFC 03/11] arm64: dts: qcom: sc8180x: " Konrad Dybcio
2024-09-18 22:57 ` [PATCH RFC 04/11] arm64: dts: qcom: sc8280xp: " Konrad Dybcio
2024-09-18 22:57 ` [PATCH RFC 05/11] arm64: dts: qcom: sdm670: " Konrad Dybcio
2024-09-18 22:57 ` [PATCH RFC 06/11] arm64: dts: qcom: sdm845: " Konrad Dybcio
2024-09-18 22:57 ` [PATCH RFC 07/11] arm64: dts: qcom: sm6350: " Konrad Dybcio
2024-09-24 7:15 ` Luca Weiss
2024-09-24 7:37 ` Luca Weiss
2024-09-24 10:04 ` Konrad Dybcio
2024-09-18 22:57 ` [PATCH RFC 08/11] arm64: dts: qcom: sm8150: " Konrad Dybcio
2024-09-18 22:57 ` [PATCH RFC 09/11] arm64: dts: qcom: sm8350: " Konrad Dybcio
2024-09-18 22:57 ` [PATCH RFC 10/11] arm64: dts: qcom: sm8450: " Konrad Dybcio
2024-09-18 22:57 ` [PATCH RFC 11/11] arm64: dts: qcom: x1e80100: " Konrad Dybcio
2024-09-19 7:00 ` [RFC PATCH 00/11] Affirm SMMU coherent pagetable walker capability on RPMh SoCs Luca Weiss
2024-09-19 10:07 ` Konrad Dybcio [this message]
2024-09-19 18:48 ` Steev Klimaszewski
2024-09-20 7:35 ` neil.armstrong
2024-10-07 14:25 ` Bjorn Andersson
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=2fb16b35-e6c5-4239-a745-a9dd7412539a@kernel.org \
--to=konradybcio@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=marijn.suijten@somainline.org \
--cc=quic_kdybcio@quicinc.com \
--cc=robh@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).