From: Jason Gunthorpe <jgg@nvidia.com>
To: Will Deacon <will@kernel.org>
Cc: Joerg Roedel <joro@8bytes.org>,
Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
catalin.marinas@arm.com, kernel-team@android.com,
Michael Shavit <mshavit@google.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
Joerg Roedel <jroedel@suse.de>,
Lu Baolu <baolu.lu@linux.intel.com>,
Mostafa Saleh <smostafa@google.com>,
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
Moritz Fischer <moritzf@google.com>,
Zhangfei Gao <zhangfei.gao@linaro.org>,
Nicolin Chen <nicolinc@nvidia.com>,
patches@lists.linux.dev, Moritz Fischer <mdf@kernel.org>
Subject: Re: [PATCH v6 00/16] Update SMMUv3 to the modern iommu API (part 1/3)
Date: Thu, 29 Feb 2024 16:23:31 -0400 [thread overview]
Message-ID: <20240229202331.GL9179@nvidia.com> (raw)
In-Reply-To: <170921954415.3073552.7948276252050662200.b4-ty@kernel.org>
On Thu, Feb 29, 2024 at 04:34:13PM +0000, Will Deacon wrote:
> On Mon, 26 Feb 2024 13:07:11 -0400, Jason Gunthorpe wrote:
> > The SMMUv3 driver was originally written in 2015 when the iommu driver
> > facing API looked quite different. The API has evolved, especially lately,
> > and the driver has fallen behind.
> >
> > This work aims to bring make the SMMUv3 driver the best IOMMU driver with
> > the most comprehensive implementation of the API. After all parts it
> > addresses:
> >
> > [...]
>
> Applied to will (for-joerg/arm-smmu/updates), thanks!
Thanks Will! I'll post the rebased part 2 and start getting tags
hopefully next week (I got a flu, just getting back to work now).
Did you notice any contentious patches in there that could use more
attention?
https://lore.kernel.org/linux-iommu/0-v4-e7091cdd9e8d+43b1-smmuv3_newapi_p2_jgg@nvidia.com/
Jason
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Will Deacon <will@kernel.org>
Cc: Joerg Roedel <joro@8bytes.org>,
Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
catalin.marinas@arm.com, kernel-team@android.com,
Michael Shavit <mshavit@google.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
Joerg Roedel <jroedel@suse.de>,
Lu Baolu <baolu.lu@linux.intel.com>,
Mostafa Saleh <smostafa@google.com>,
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
Moritz Fischer <moritzf@google.com>,
Zhangfei Gao <zhangfei.gao@linaro.org>,
Nicolin Chen <nicolinc@nvidia.com>,
patches@lists.linux.dev, Moritz Fischer <mdf@kernel.org>
Subject: Re: [PATCH v6 00/16] Update SMMUv3 to the modern iommu API (part 1/3)
Date: Thu, 29 Feb 2024 16:23:31 -0400 [thread overview]
Message-ID: <20240229202331.GL9179@nvidia.com> (raw)
In-Reply-To: <170921954415.3073552.7948276252050662200.b4-ty@kernel.org>
On Thu, Feb 29, 2024 at 04:34:13PM +0000, Will Deacon wrote:
> On Mon, 26 Feb 2024 13:07:11 -0400, Jason Gunthorpe wrote:
> > The SMMUv3 driver was originally written in 2015 when the iommu driver
> > facing API looked quite different. The API has evolved, especially lately,
> > and the driver has fallen behind.
> >
> > This work aims to bring make the SMMUv3 driver the best IOMMU driver with
> > the most comprehensive implementation of the API. After all parts it
> > addresses:
> >
> > [...]
>
> Applied to will (for-joerg/arm-smmu/updates), thanks!
Thanks Will! I'll post the rebased part 2 and start getting tags
hopefully next week (I got a flu, just getting back to work now).
Did you notice any contentious patches in there that could use more
attention?
https://lore.kernel.org/linux-iommu/0-v4-e7091cdd9e8d+43b1-smmuv3_newapi_p2_jgg@nvidia.com/
Jason
next prev parent reply other threads:[~2024-02-29 20:23 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 17:07 [PATCH v6 00/16] Update SMMUv3 to the modern iommu API (part 1/3) Jason Gunthorpe
2024-02-26 17:07 ` Jason Gunthorpe
2024-02-26 17:07 ` [PATCH v6 01/16] iommu/arm-smmu-v3: Make STE programming independent of the callers Jason Gunthorpe
2024-02-26 17:07 ` Jason Gunthorpe
2024-02-27 12:47 ` Will Deacon
2024-02-27 12:47 ` Will Deacon
2024-02-29 14:07 ` Jason Gunthorpe
2024-02-29 14:07 ` Jason Gunthorpe
2024-02-26 17:07 ` [PATCH v6 02/16] iommu/arm-smmu-v3: Consolidate the STE generation for abort/bypass Jason Gunthorpe
2024-02-26 17:07 ` Jason Gunthorpe
2024-02-26 17:07 ` [PATCH v6 03/16] iommu/arm-smmu-v3: Move the STE generation for S1 and S2 domains into functions Jason Gunthorpe
2024-02-26 17:07 ` Jason Gunthorpe
2024-02-26 17:07 ` [PATCH v6 04/16] iommu/arm-smmu-v3: Build the whole STE in arm_smmu_make_s2_domain_ste() Jason Gunthorpe
2024-02-26 17:07 ` Jason Gunthorpe
2024-02-26 17:07 ` [PATCH v6 05/16] iommu/arm-smmu-v3: Hold arm_smmu_asid_lock during all of attach_dev Jason Gunthorpe
2024-02-26 17:07 ` Jason Gunthorpe
2024-02-26 17:07 ` [PATCH v6 06/16] iommu/arm-smmu-v3: Compute the STE only once for each master Jason Gunthorpe
2024-02-26 17:07 ` Jason Gunthorpe
2024-02-26 17:07 ` [PATCH v6 07/16] iommu/arm-smmu-v3: Do not change the STE twice during arm_smmu_attach_dev() Jason Gunthorpe
2024-02-26 17:07 ` Jason Gunthorpe
2024-02-26 17:07 ` [PATCH v6 08/16] iommu/arm-smmu-v3: Put writing the context descriptor in the right order Jason Gunthorpe
2024-02-26 17:07 ` Jason Gunthorpe
2024-02-26 17:07 ` [PATCH v6 09/16] iommu/arm-smmu-v3: Pass smmu_domain to arm_enable/disable_ats() Jason Gunthorpe
2024-02-26 17:07 ` Jason Gunthorpe
2024-02-26 17:07 ` [PATCH v6 10/16] iommu/arm-smmu-v3: Remove arm_smmu_master->domain Jason Gunthorpe
2024-02-26 17:07 ` Jason Gunthorpe
2024-02-26 17:07 ` [PATCH v6 11/16] iommu/arm-smmu-v3: Check that the RID domain is S1 in SVA Jason Gunthorpe
2024-02-26 17:07 ` Jason Gunthorpe
2024-02-26 17:07 ` [PATCH v6 12/16] iommu/arm-smmu-v3: Add a global static IDENTITY domain Jason Gunthorpe
2024-02-26 17:07 ` Jason Gunthorpe
2024-02-26 17:07 ` [PATCH v6 13/16] iommu/arm-smmu-v3: Add a global static BLOCKED domain Jason Gunthorpe
2024-02-26 17:07 ` Jason Gunthorpe
2024-02-26 17:07 ` [PATCH v6 14/16] iommu/arm-smmu-v3: Use the identity/blocked domain during release Jason Gunthorpe
2024-02-26 17:07 ` Jason Gunthorpe
2024-02-26 17:07 ` [PATCH v6 15/16] iommu/arm-smmu-v3: Pass arm_smmu_domain and arm_smmu_device to finalize Jason Gunthorpe
2024-02-26 17:07 ` Jason Gunthorpe
2024-02-26 17:07 ` [PATCH v6 16/16] iommu/arm-smmu-v3: Convert to domain_alloc_paging() Jason Gunthorpe
2024-02-26 17:07 ` Jason Gunthorpe
2024-02-29 16:34 ` [PATCH v6 00/16] Update SMMUv3 to the modern iommu API (part 1/3) Will Deacon
2024-02-29 16:34 ` Will Deacon
2024-02-29 20:23 ` Jason Gunthorpe [this message]
2024-02-29 20:23 ` Jason Gunthorpe
2024-02-29 20:47 ` Nicolin Chen
2024-02-29 20:47 ` Nicolin Chen
2024-03-01 8:01 ` Will Deacon
2024-03-01 8:01 ` Will Deacon
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=20240229202331.GL9179@nvidia.com \
--to=jgg@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mdf@kernel.org \
--cc=moritzf@google.com \
--cc=mshavit@google.com \
--cc=nicolinc@nvidia.com \
--cc=patches@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=smostafa@google.com \
--cc=will@kernel.org \
--cc=zhangfei.gao@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.