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: Jingqi Liu <Jingqi.liu@intel.com>,
	Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] [PULL REQUEST] Intel IOMMU updates for Linux v6.7
Date: Mon, 16 Oct 2023 11:28:26 +0800	[thread overview]
Message-ID: <20231016032830.101321-1-baolu.lu@linux.intel.com> (raw)

Hi Joerg,

The following patches have been queued for v6.7. They aim to:

 - Enable debugfs to dump domain attached to a pasid
 - Remove an unnecessary inline function.

All patches are based on v6.6-rc5. The series is also available at:
https://github.com/LuBaolu/intel-iommu/commits/vtd-update-for-v6.7

Please consider them for v6.7.

Best regards,
Baolu

Jiapeng Chong (1):
  iommu/vt-d: Remove unused function

Jingqi Liu (3):
  iommu/vt-d: debugfs: Dump entry pointing to huge page
  iommu/vt-d: debugfs: Create/remove debugfs file per {device, pasid}
  iommu/vt-d: debugfs: Support dumping a specified page table

 drivers/iommu/intel/iommu.h   |  14 +++
 drivers/iommu/intel/debugfs.c | 215 +++++++++++++++++++++++++++-------
 drivers/iommu/intel/iommu.c   |   7 ++
 drivers/iommu/intel/pasid.c   |   9 --
 4 files changed, 195 insertions(+), 50 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-10-16  3:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-16  3:28 Lu Baolu [this message]
2023-10-16  3:28 ` [PATCH 1/4] iommu/vt-d: Remove unused function Lu Baolu
2023-10-16  3:28 ` [PATCH 2/4] iommu/vt-d: debugfs: Dump entry pointing to huge page Lu Baolu
2023-10-16  3:28 ` [PATCH 3/4] iommu/vt-d: debugfs: Create/remove debugfs file per {device, pasid} Lu Baolu
2023-10-16  3:28 ` [PATCH 4/4] iommu/vt-d: debugfs: Support dumping a specified page table Lu Baolu
2023-10-16  7:36 ` [PATCH 0/4] [PULL REQUEST] Intel IOMMU updates for Linux v6.7 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=20231016032830.101321-1-baolu.lu@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=Jingqi.liu@intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jiapeng.chong@linux.alibaba.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.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 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.