public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Yi Liu <yi.l.liu@intel.com>, Arnd Bergmann <arnd@arndb.de>,
	Kevin Tian <kevin.tian@intel.com>,
	Joao Martins <joao.m.martins@oracle.com>,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 00/10] [PULL REQUEST] iommu/vt-d: Fixes for v6.8-rc5
Date: Mon, 19 Feb 2024 19:15:51 +0800	[thread overview]
Message-ID: <20240219111601.96405-1-baolu.lu@linux.intel.com> (raw)

Hi Joerg,

The following patches have been queued for v6.8. They fix some missed
behavior for nested domain implementation in the Intel IOMMU driver. To
be more specific, they aim to achieve comprehensive:

- Cache invalidation for changes in a parent domain;
- Dirty tracking setting for parent and nested domains;
- Fix a constant-out-of-range warning.

As the nested domain implementation in the Intel IOMMU driver was
introduced in v6.8-rc1, I would suggest merging this series in the rc
phase. So,

Please consider them for the iommu/fix branch.

Best regards,
Lu Baolu

Arnd Bergmann (1):
  iommu/vt-d: Fix constant-out-of-range warning

Yi Liu (9):
  iommu/vt-d: Track nested domains in parent
  iommu/vt-d: Add __iommu_flush_iotlb_psi()
  iommu/vt-d: Add missing iotlb flush for parent domain
  iommu/vt-d: Update iotlb in nested domain attach
  iommu/vt-d: Add missing device iotlb flush for parent domain
  iommu/vt-d: Remove domain parameter for
    intel_pasid_setup_dirty_tracking()
  iommu/vt-d: Wrap the dirty tracking loop to be a helper
  iommu/vt-d: Add missing dirty tracking set for parent domain
  iommu/vt-d: Set SSADE when attaching to a parent with dirty tracking

 drivers/iommu/intel/iommu.h  |   7 ++
 drivers/iommu/intel/pasid.h  |   1 -
 drivers/iommu/intel/iommu.c  | 214 ++++++++++++++++++++++++++---------
 drivers/iommu/intel/nested.c |  16 ++-
 drivers/iommu/intel/pasid.c  |   5 +-
 5 files changed, 187 insertions(+), 56 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-02-19 11:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19 11:15 Lu Baolu [this message]
2024-02-19 11:15 ` [PATCH 01/10] iommu/vt-d: Track nested domains in parent Lu Baolu
2024-02-19 11:15 ` [PATCH 02/10] iommu/vt-d: Add __iommu_flush_iotlb_psi() Lu Baolu
2024-02-19 11:15 ` [PATCH 03/10] iommu/vt-d: Add missing iotlb flush for parent domain Lu Baolu
2024-02-19 11:15 ` [PATCH 04/10] iommu/vt-d: Update iotlb in nested domain attach Lu Baolu
2024-02-19 11:15 ` [PATCH 05/10] iommu/vt-d: Add missing device iotlb flush for parent domain Lu Baolu
2024-02-19 11:15 ` [PATCH 06/10] iommu/vt-d: Remove domain parameter for intel_pasid_setup_dirty_tracking() Lu Baolu
2024-02-19 11:15 ` [PATCH 07/10] iommu/vt-d: Wrap the dirty tracking loop to be a helper Lu Baolu
2024-02-19 11:15 ` [PATCH 08/10] iommu/vt-d: Add missing dirty tracking set for parent domain Lu Baolu
2024-02-19 11:16 ` [PATCH 09/10] iommu/vt-d: Set SSADE when attaching to a parent with dirty tracking Lu Baolu
2024-02-19 11:16 ` [PATCH 10/10] iommu/vt-d: Fix constant-out-of-range warning Lu Baolu
2024-02-21  9:29 ` [PATCH 00/10] [PULL REQUEST] iommu/vt-d: Fixes for v6.8-rc5 Joerg Roedel

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=20240219111601.96405-1-baolu.lu@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=iommu@lists.linux.dev \
    --cc=joao.m.martins@oracle.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.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