Archive-only list for patches
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: iommu@lists.linux.dev, Robin Murphy <robin.murphy@arm.com>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	Will Deacon <will@kernel.org>,
	Alejandro Jimenez <alejandro.j.jimenez@oracle.com>,
	Joerg Roedel <jroedel@suse.de>, Kevin Tian <kevin.tian@intel.com>,
	patches@lists.linux.dev, Vasant Hegde <vasant.hegde@amd.com>
Subject: Re: [PATCH v2 0/7] iommu/amd: Cleanup some of the domain_alloc_paging path
Date: Fri, 17 Jan 2025 08:59:54 +0100	[thread overview]
Message-ID: <Z4oN-qjcKN-89yuq@8bytes.org> (raw)
In-Reply-To: <0-v2-9776c53c2966+1c7-amd_paging_flags_jgg@nvidia.com>

On Fri, Jan 10, 2025 at 12:34:58PM -0400, Jason Gunthorpe wrote:
> This is a small collection of cleanups
>  - Remove amd_iommu_domain_update() (dead code)
>  - Remove domain_alloc()
>  - Remove now obsolete NULL checks
>  - Remove obsolete domain types in the domain_alloc_paging_flags() flow
>  - Use PD_MODE consistently instead of mixing with io_pgtable stuff
> 
> v2:
>  - Remove bitmasking from switch in amd_iommu_domain_alloc_paging_flags()
>  - Update commit messages with comments
> v1: https://patch.msgid.link/r/0-v1-cf88773f22d1+39bd-amd_paging_flags_jgg@nvidia.com
> 
> Alejandro Jimenez (1):
>   iommu/amd: Remove unused amd_iommu_domain_update()
> 
> Jason Gunthorpe (6):
>   iommu/amd: Remove domain_alloc()
>   iommu/amd: Remove dev == NULL checks
>   iommu/amd: Remove type argument from do_iommu_domain_alloc() and
>     related
>   iommu/amd: Change amd_iommu_pgtable to use enum protection_domain_mode
>   iommu/amd: Move the nid to pdom_setup_pgtable()
>   iommu/amd: Fully decode all combinations of alloc_paging_flags
> 
>  drivers/iommu/amd/amd_iommu.h |   5 +-
>  drivers/iommu/amd/init.c      |  14 ++--
>  drivers/iommu/amd/iommu.c     | 144 ++++++++++------------------------
>  drivers/iommu/amd/pasid.c     |   3 +-
>  4 files changed, 54 insertions(+), 112 deletions(-)

Applied, thanks.

      parent reply	other threads:[~2025-01-17  7:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10 16:34 [PATCH v2 0/7] iommu/amd: Cleanup some of the domain_alloc_paging path Jason Gunthorpe
2025-01-10 16:34 ` [PATCH v2 1/7] iommu/amd: Remove unused amd_iommu_domain_update() Jason Gunthorpe
2025-01-10 16:35 ` [PATCH v2 2/7] iommu/amd: Remove domain_alloc() Jason Gunthorpe
2025-01-10 16:35 ` [PATCH v2 3/7] iommu/amd: Remove dev == NULL checks Jason Gunthorpe
2025-01-10 16:35 ` [PATCH v2 4/7] iommu/amd: Remove type argument from do_iommu_domain_alloc() and related Jason Gunthorpe
2025-01-10 16:35 ` [PATCH v2 5/7] iommu/amd: Change amd_iommu_pgtable to use enum protection_domain_mode Jason Gunthorpe
2025-01-10 16:35 ` [PATCH v2 6/7] iommu/amd: Move the nid to pdom_setup_pgtable() Jason Gunthorpe
2025-01-10 16:35 ` [PATCH v2 7/7] iommu/amd: Fully decode all combinations of alloc_paging_flags Jason Gunthorpe
2025-01-17  7:59 ` Joerg Roedel [this message]

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=Z4oN-qjcKN-89yuq@8bytes.org \
    --to=joro@8bytes.org \
    --cc=alejandro.j.jimenez@oracle.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=jroedel@suse.de \
    --cc=kevin.tian@intel.com \
    --cc=patches@lists.linux.dev \
    --cc=robin.murphy@arm.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=vasant.hegde@amd.com \
    --cc=will@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