public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: iommu@lists.linux.dev
Cc: baolu.lu@linux.intel.com, Joerg Roedel <joro@8bytes.org>,
	Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
	Yi Liu <yi.l.liu@intel.com>, Vasant Hegde <vasant.hegde@amd.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/7] iommu/vt-d: Add domain_alloc_paging support
Date: Tue, 29 Oct 2024 12:38:00 +0800	[thread overview]
Message-ID: <ba234a15-2feb-4c52-83e1-e427010fc1fc@linux.intel.com> (raw)
In-Reply-To: <20241021085125.192333-1-baolu.lu@linux.intel.com>

On 2024/10/21 16:51, Lu Baolu wrote:
> The Intel iommu driver will now use the domain_alloc_paging callback and
> remove the legacy domain_alloc callback. This ensures that a valid
> device pointer is provided whenever a paging domain is allocated, and
> all dmar_domain attributes can be set up at the time of allocation.
> 
> Both first-stage and second-stage page tables can be used for a paging
> domain. Unless IOMMU_HWPT_ALLOC_NEST_PARENT or
> IOMMU_HWPT_ALLOC_DIRTY_TRACKING is specified during paging domain
> allocation, this driver will try to use first-stage page tables if the
> hardware is capable. This is assuming that the first-stage page table is
> compatible with both the host and guest kernels.
> 
> The whole series is also available on GitHub:
> https://github.com/LuBaolu/intel-iommu/commits/vtd-domain_alloc_paging-v2
> 
> Please help review and comment.
> 
> Change log:
> 
> v2:
>   - Make prepare_domain_attach_device() a specific helper to check
>     whether a paging domain is compatible with the iommu hardware
>     capability.
>   - Rename prepare_domain_attach_device() to paging_domain_compatible()
>     to make it more meaningful.
> 
> v1:https://lore.kernel.org/linux-iommu/20241011042722.73930-1- 
> baolu.lu@linux.intel.com/
> 
> Lu Baolu (7):
>    iommu/vt-d: Add domain_alloc_paging support
>    iommu/vt-d: Remove unused domain_alloc callback
>    iommu/vt-d: Enhance compatibility check for paging domain attach
>    iommu/vt-d: Remove domain_update_iommu_cap()
>    iommu/vt-d: Remove domain_update_iommu_superpage()
>    iommu/vt-d: Refactor first_level_by_default()
>    iommu/vt-d: Refine intel_iommu_domain_alloc_user()
> 
>   drivers/iommu/intel/iommu.h  |   4 +-
>   drivers/iommu/intel/iommu.c  | 328 +++++++----------------------------
>   drivers/iommu/intel/nested.c |   2 +-
>   drivers/iommu/intel/pasid.c  |  28 +--
>   4 files changed, 64 insertions(+), 298 deletions(-)

Queued for v6.13.

--
baolu

      parent reply	other threads:[~2024-10-29  4:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21  8:51 [PATCH v2 0/7] iommu/vt-d: Add domain_alloc_paging support Lu Baolu
2024-10-21  8:51 ` [PATCH v2 1/7] " Lu Baolu
2024-10-21 12:44   ` Jason Gunthorpe
2024-10-21  8:51 ` [PATCH v2 2/7] iommu/vt-d: Remove unused domain_alloc callback Lu Baolu
2024-10-21  8:51 ` [PATCH v2 3/7] iommu/vt-d: Enhance compatibility check for paging domain attach Lu Baolu
2024-10-21 12:46   ` Jason Gunthorpe
2024-10-22  1:20     ` Baolu Lu
2024-10-21  8:51 ` [PATCH v2 4/7] iommu/vt-d: Remove domain_update_iommu_cap() Lu Baolu
2024-10-21  8:51 ` [PATCH v2 5/7] iommu/vt-d: Remove domain_update_iommu_superpage() Lu Baolu
2024-10-21  8:51 ` [PATCH v2 6/7] iommu/vt-d: Refactor first_level_by_default() Lu Baolu
2024-10-21  8:51 ` [PATCH v2 7/7] iommu/vt-d: Refine intel_iommu_domain_alloc_user() Lu Baolu
2024-10-29  4:38 ` Baolu Lu [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=ba234a15-2feb-4c52-83e1-e427010fc1fc@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=vasant.hegde@amd.com \
    --cc=will@kernel.org \
    --cc=yi.l.liu@intel.com \
    /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