linux-kernel - Re: [PATCH 0/3] iommu/arm-smmu: introduction of ACTLR implementation for Qualcomm SoCs

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: <6c4bd8fd-624a-4c2f-a9a8-dfdbd8281010@quicinc.com>
Date:   Mon, 6 Nov 2023 12:09:26 +0530
From:   Bibek Kumar Patro <quic_bibekkum@...cinc.com>
To:     Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
CC:     <will@...nel.org>, <robin.murphy@....com>, <joro@...tes.org>,
        <a39.skl@...il.com>, <konrad.dybcio@...aro.org>,
        <quic_saipraka@...cinc.com>, <quic_pkondeti@...cinc.com>,
        <quic_molvera@...cinc.com>, <linux-arm-kernel@...ts.infradead.org>,
        <iommu@...ts.linux.dev>, <linux-kernel@...r.kernel.org>,
        <qipl.kernel.upstream@...cinc.com>
Subject: Re: [PATCH 0/3] iommu/arm-smmu: introduction of ACTLR implementation
 for Qualcomm SoCs



On 11/4/2023 4:14 AM, Dmitry Baryshkov wrote:
> On Fri, 3 Nov 2023 at 23:53, Bibek Kumar Patro
> <quic_bibekkum@...cinc.com> wrote:
>>
>> This patch series consists of three parts and covers the following:
>>
>> 1. Introducing intital set of driver changes to implement ACTLR register
>> for custom prefetcher settings in Qualcomm SoCs.
>>
>> 2. Adding ACTLR data and implementation operations for SM8550.
>>
>> 3. Re-enabling context caching for Qualcomm SoCs to retain prefetcher
>> settings during reset and runtime suspend.
>>
>> Link to discussion on RFC posted on ACTLR implementation:
>> https://lore.kernel.org/all/a01e7e60-6ead-4a9e-ba90-22a8a6bbd03f@quicinc.com/
> 
> First two patches in that thread were not archived for some reason.
> 
> However, as there was a previous iteration, it is suggested to include
> the changelog between RFC and v1.
> 

Right, in the initial RFC sent somehow only the replies were archived.
Although the RFC patch was a WIP patch in rough state, sent to take 
upstream inputs.
Will try adding the changelog in v2.
To give a context, in the RFC patch, we we're initially proposing a dt
based approach to set the actlr property, where we would piggyback on 
the iommus property to store actlr value and set the property during
smmu device probe.

>>
>> Bibek Kumar Patro (3):
>>    iommu/arm-smmu: introduction of ACTLR for custom prefetcher settings
>>    iommu/arm-smmu: add ACTLR data and support for sm8550
>>    iommu/arm-smmu: re-enable context caching in smmu reset operation
>>
>>   drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 143 ++++++++++++++++++++-
>>   drivers/iommu/arm/arm-smmu/arm-smmu-qcom.h |   2 +
> 
> Although it is not mentioned in the MAINTAINERS file, could you please
> CC linux-arm-msm when sending v2?
> 

Sure Dmitry, will take care of this and CC linux-arm-msm while sending v2.

>>   drivers/iommu/arm/arm-smmu/arm-smmu.c      |   5 +-
>>   drivers/iommu/arm/arm-smmu/arm-smmu.h      |   5 +
>>   4 files changed, 146 insertions(+), 9 deletions(-)
>>
>> --
>> 2.17.1
>>
> 
>