All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Jason Gunthorpe <jgg@nvidia.com>, Kees Bakker <kees@ijzerbout.nl>,
	Zhenzhong Duan <zhenzhong.duan@intel.com>,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] [PULL REQUEST] Intel IOMMU updates for v6.14
Date: Tue,  7 Jan 2025 10:17:41 +0800	[thread overview]
Message-ID: <20250107021746.6908-1-baolu.lu@linux.intel.com> (raw)

Hi Joerg,

The following changes have been queued for v6.14-rc1. They are about new
features and code refactoring, including:

 - Remove domain_alloc_paging()
 - Remove capability audit code
 - Draining PRQ in sva unbind path when FPD bit set
 - Link cache tags of same iommu unit together

These patches are based on v6.13-rc6. The complete patches are also
available at:

https://github.com/LuBaolu/intel-iommu/commits/vtd-update-for-v6.14

Please consider them for iommu next.

Best regards,
baolu

Jason Gunthorpe (1):
  iommu/vt-d: Remove domain_alloc_paging()

Kees Bakker (1):
  iommu/vt-d: Avoid use of NULL after WARN_ON_ONCE

Lu Baolu (2):
  iommu/vt-d: Remove iommu cap audit
  iommu/vt-d: Draining PRQ in sva unbind path when FPD bit set

Zhenzhong Duan (1):
  iommu/vt-d: Link cache tags of same iommu unit together

 drivers/iommu/intel/Makefile        |   2 +-
 drivers/iommu/intel/cache.c         |  11 +-
 drivers/iommu/intel/cap_audit.c     | 217 ----------------------------
 drivers/iommu/intel/cap_audit.h     | 131 -----------------
 drivers/iommu/intel/iommu.c         |  32 +---
 drivers/iommu/intel/irq_remapping.c |   8 -
 drivers/iommu/intel/pasid.c         |  22 ++-
 drivers/iommu/intel/pasid.h         |   6 +
 8 files changed, 42 insertions(+), 387 deletions(-)
 delete mode 100644 drivers/iommu/intel/cap_audit.c
 delete mode 100644 drivers/iommu/intel/cap_audit.h

-- 
2.43.0


             reply	other threads:[~2025-01-07  2:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07  2:17 Lu Baolu [this message]
2025-01-07  2:17 ` [PATCH 1/5] iommu/vt-d: Avoid use of NULL after WARN_ON_ONCE Lu Baolu
2025-01-07  2:17 ` [PATCH 2/5] iommu/vt-d: Remove domain_alloc_paging() Lu Baolu
2025-01-07  2:17 ` [PATCH 3/5] iommu/vt-d: Remove iommu cap audit Lu Baolu
2025-01-07  2:17 ` [PATCH 4/5] iommu/vt-d: Draining PRQ in sva unbind path when FPD bit set Lu Baolu
2025-01-07  2:17 ` [PATCH 5/5] iommu/vt-d: Link cache tags of same iommu unit together Lu Baolu
2025-01-07  8:32 ` [PATCH 0/5] [PULL REQUEST] Intel IOMMU updates for v6.14 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=20250107021746.6908-1-baolu.lu@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kees@ijzerbout.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhenzhong.duan@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 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.