public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: LKML <linux-kernel@vger.kernel.org>,
	iommu@lists.linux.dev, "Lu Baolu" <baolu.lu@linux.intel.com>,
	Joerg Roedel <joro@8bytes.org>,
	Jean-Philippe Brucker <jean-philippe@linaro.com>,
	"Robin Murphy" <robin.murphy@arm.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Raj Ashok <ashok.raj@intel.com>,
	"Tian, Kevin" <kevin.tian@intel.com>, Yi Liu <yi.l.liu@intel.com>,
	Jason Gunthorpe <jgg@nvidia.com>,
	Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: [PATCH 0/2] Remove VT-d virtual command interface
Date: Fri, 10 Feb 2023 15:02:04 -0800	[thread overview]
Message-ID: <20230210230206.3160144-1-jacob.jun.pan@linux.intel.com> (raw)

Hi all,

This patch set removes unused VT-d virtual command interface followed by
clean up in the IOASID code.

This has only been tested on x86 platforms, need help with testing on ARM
SMMU and other architectures.

I also hope to collect feedback on the upcoming clean up and enhancements
below:
1. Consolidate VT-d private SVA PASID array with IOASID common code
2. As we retain the global IOASID allocator, we need some level of resource
management. I want to restart the effort to include IOASID under misc
cgroup.
(https://lore.kernel.org/linux-iommu/20210303160205.151d114e@jacob-builder/)

Thanks,

Jacob

Jacob Pan (2):
  iommu/vt-d: Remove virtual command interface
  iommu/ioasid: Remove custom IOASID allocator

 drivers/iommu/intel/cap_audit.c |   2 -
 drivers/iommu/intel/dmar.c      |   2 -
 drivers/iommu/intel/iommu.c     |  85 ---------
 drivers/iommu/intel/iommu.h     |   8 -
 drivers/iommu/ioasid.c          | 293 +-------------------------------
 include/linux/ioasid.h          |  28 ---
 6 files changed, 9 insertions(+), 409 deletions(-)

-- 
2.25.1


             reply	other threads:[~2023-02-10 22:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 23:02 Jacob Pan [this message]
2023-02-10 23:02 ` [PATCH 1/2] iommu/vt-d: Remove virtual command interface Jacob Pan
2023-02-13  2:54   ` Tian, Kevin
2023-02-13 23:19   ` Jason Gunthorpe
2023-02-10 23:02 ` [PATCH 2/2] iommu/ioasid: Remove custom IOASID allocator Jacob Pan
2023-02-13  3:14   ` Tian, Kevin
2023-02-13 16:20   ` Jean-Philippe Brucker
2023-02-13 16:24     ` Jason Gunthorpe
2023-02-13 19:11       ` Jacob Pan
2023-02-13 19:42         ` Jason Gunthorpe
2023-02-13 18:34     ` Jacob Pan
2023-02-13 19:30       ` Jean-Philippe Brucker
2023-02-13 19:48         ` Jason Gunthorpe
2023-02-13 19:39       ` Jason Gunthorpe
2023-02-13 21:44         ` Jacob Pan
2023-02-13 23:18           ` Jason Gunthorpe
2023-02-13 23:43             ` Jacob Pan
2023-02-13 23:45               ` Jason Gunthorpe
2023-02-14  6:26                 ` Tian, Kevin
2023-02-14 14:56                   ` Jason Gunthorpe
2023-02-15  1:39                     ` Tian, Kevin
2023-02-13  2:52 ` [PATCH 0/2] Remove VT-d virtual command interface Tian, Kevin

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=20230210230206.3160144-1-jacob.jun.pan@linux.intel.com \
    --to=jacob.jun.pan@linux.intel.com \
    --cc=ashok.raj@intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux.dev \
    --cc=jean-philippe@linaro.com \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --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