From: Baolu Lu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Kevin Tian <kevin.tian@intel.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Yi Liu <yi.l.liu@intel.com>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] iommu/vt-d: Remove iommu cap audit
Date: Thu, 2 Jan 2025 11:13:01 +0800 [thread overview]
Message-ID: <bcf70c0d-ea12-4149-ba9a-2001df95186b@linux.intel.com> (raw)
In-Reply-To: <20241216071828.22962-1-baolu.lu@linux.intel.com>
On 12/16/24 15:18, Lu Baolu wrote:
> The capability audit code was introduced by commit <ad3d19029979>
> "iommu/vt-d: Audit IOMMU Capabilities and add helper functions", aiming
> to verify the consistency of capabilities across all IOMMUs for supported
> features.
>
> Nowadays, all the kAPIs of the iommu subsystem have evolved to be device
> oriented, in preparation for supporting heterogeneous IOMMU architectures.
> There is no longer a need to require capability consistence among IOMMUs
> for any feature.
>
> Remove the iommu cap audit code to make the driver align with the design
> in the iommu core.
>
> Signed-off-by: Lu Baolu<baolu.lu@linux.intel.com>
> ---
> drivers/iommu/intel/Makefile | 2 +-
> drivers/iommu/intel/cap_audit.c | 217 ----------------------------
> drivers/iommu/intel/cap_audit.h | 131 -----------------
> drivers/iommu/intel/iommu.c | 9 --
> drivers/iommu/intel/irq_remapping.c | 8 -
> 5 files changed, 1 insertion(+), 366 deletions(-)
> delete mode 100644 drivers/iommu/intel/cap_audit.c
> delete mode 100644 drivers/iommu/intel/cap_audit.h
Queued for v6.14.
prev parent reply other threads:[~2025-01-02 3:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 7:18 [PATCH 1/1] iommu/vt-d: Remove iommu cap audit Lu Baolu
2024-12-17 7:39 ` Tian, Kevin
2025-01-02 3:13 ` 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=bcf70c0d-ea12-4149-ba9a-2001df95186b@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=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 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.