linux-kernel - Re: [PATCH 10/10] arm64: dts: qcom: sdm845: add LLCC BWMON

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <25321f37-dbea-188b-1b11-e983a00701b2@quicinc.com>
Date:   Tue, 26 Jul 2022 17:01:59 +0530
From:   Sibi Sankar <quic_sibis@...cinc.com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        Steev Klimaszewski <steev@...i.org>,
        Andy Gross <agross@...nel.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Konrad Dybcio <konrad.dybcio@...ainline.org>,
        Georgi Djakov <djakov@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        <linux-arm-msm@...r.kernel.org>, <linux-pm@...r.kernel.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
CC:     Rajendra Nayak <quic_rjendra@...cinc.com>
Subject: Re: [PATCH 10/10] arm64: dts: qcom: sdm845: add LLCC BWMON

On 7/23/22 2:06 PM, Krzysztof Kozlowski wrote:
> On 23/07/2022 04:37, Steev Klimaszewski wrote:
>>>
>>> Currently it's 5.19.0-rc7 (torvalds tree at 4ba1329c) with a few extra
>>> patches on top, the bwmon set included.  It's possible that secure
>>> world uses it, but I do not know enough about that to say one way or
>>> the other.
> 
> To test patches you should apply them on maintainer's tree or
> linux-next. Applying on other trees of course might be useful for
> testing some backports, but it is independent process and different issue.
> 
>>>
>>> -- steev
>>>
>> I think you may be right; I just applied this patchset to -next
>> (20220722) and i do not see the error message there.  On my 5.19-rc7
>> tree, i am also testing a patchset that enables qcom devices to access
>> efivars, so possibly we are ending up in secure world there?
> 
> Actually mapping of IO space should not touch secure world, so this was
> a long shot assuming you test it on the next.
> 

The memory region specified in device tree overlaps with the llcc system
cache controller node. Steev probably had the QCOM_LLCC config enabled 
when he tested it out on his branch.

> 
> Best regards,
> Krzysztof
>