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: <20200507103129.GA29541@willie-the-truck>
Date:   Thu, 7 May 2020 11:31:29 +0100
From:   Will Deacon <will@...nel.org>
To:     Sai Prakash Ranjan <saiprakash.ranjan@...eaurora.org>
Cc:     Robin Murphy <robin.murphy@....com>,
        Joerg Roedel <joro@...tes.org>,
        Sibi Sankar <sibis@...eaurora.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Jordan Crouse <jcrouse@...eaurora.org>,
        Rob Clark <robdclark@...il.com>, jroedel@...e.de,
        Stephen Boyd <swboyd@...omium.org>,
        iommu@...ts.linux-foundation.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-arm-msm@...r.kernel.org,
        Matthias Kaehlcke <mka@...omium.org>,
        Evan Green <evgreen@...omium.org>,
        linux-arm-msm-owner@...r.kernel.org
Subject: Re: [PATCHv4 0/6] iommu/arm-smmu: Allow client devices to select
 identity mapping

On Thu, May 07, 2020 at 03:58:06PM +0530, Sai Prakash Ranjan wrote:
> Hi Will, Joerg
> 
> On 2020-04-21 00:03, Sai Prakash Ranjan wrote:
> > This series allows DRM, Modem devices to set a default
> > identity mapping in qcom smmu implementation.
> > 
> > Patch 1 is cleanup to support other SoCs to call into
> > QCOM specific  implementation.
> > Patch 2 sets the default identity domain for DRM devices.
> > Patch 3 implements def_domain_type callback for arm-smmu.
> > Patch 4 sets the default identity domain for modem device.
> > Patch 5-6 adds the iommus property for mss pil.
> > 
> > This is based on Joerg's tree:
> >  -
> > https://git.kernel.org/pub/scm/linux/kernel/git/joro/linux.git/log/?h=iommu-probe-device-v2
> > 
> > v4:
> >  * Updated commit msg for mss pil requesting direct mapping
> > 
> > v3:
> >  * Use arm_smmu_master_cfg to get impl instead of long way as per Robin.
> >  * Use def_domain_type name for the callback in arm_smmu_imp as per
> > Robin
> > 
> > Jordan Crouse (1):
> >   iommu/arm-smmu: Allow client devices to select direct mapping
> > 
> > Sai Prakash Ranjan (2):
> >   iommu: arm-smmu-impl: Convert to a generic reset implementation
> >   iommu/arm-smmu: Implement iommu_ops->def_domain_type call-back
> > 
> > Sibi Sankar (3):
> >   iommu/arm-smmu-qcom: Request direct mapping for modem device
> >   dt-bindings: remoteproc: qcom: Add iommus property
> >   arm64: dts: qcom: sdm845-cheza: Add iommus property
> > 
> >  .../bindings/remoteproc/qcom,q6v5.txt         |  3 ++
> >  arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi    |  5 +++
> >  drivers/iommu/arm-smmu-impl.c                 |  8 ++--
> >  drivers/iommu/arm-smmu-qcom.c                 | 37 +++++++++++++++++--
> >  drivers/iommu/arm-smmu.c                      | 12 ++++++
> >  drivers/iommu/arm-smmu.h                      |  1 +
> >  6 files changed, 60 insertions(+), 6 deletions(-)
> 
> This series is reviewed by Robin.
> Any chance this series can make it to 5.8?

I'm planning to queue smmu stuff next week, been busy with arm64 stuff
so far, sorry.

Will

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ