From: Wei Wang <wei.w.wang@intel.com>
To: dwmw2@infradead.org, baolu.lu@linux.intel.com,
kevin.tian@intel.com, yi.l.liu@intel.com, jroedel@suse.de,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Cc: Wei Wang <wei.w.wang@intel.com>
Subject: [PATCH v1 0/3] Improve ATS Support Check in IOMMU/VT-d
Date: Fri, 9 May 2025 22:00:18 +0800 [thread overview]
Message-ID: <20250509140021.4029303-1-wei.w.wang@intel.com> (raw)
This patchset makes a few cleanups and fixes related to the check of ATS
support in iommu/vt-d. The first patch removes a duplicate call to
pci_physfn() in dmar_find_matched_satc_unit(). The second patch changes
dmar_ats_supported() to return boolean, aligning with the convention used
by other *_supported() functions. The third one addresses a corner case
where an integrated device, not recommended by the SATC structure, could
be incorrectly reported as "supported=true" by dmar_ats_supported().
Wei Wang (3):
iommu/vt-d: Eliminate pci_physfn() in dmar_find_matched_satc_unit()
iommu/vt-d: Change dmar_ats_supported() to return boolean
iommu/vt-d: Fix ATS support check for integrated endpoints
drivers/iommu/intel/iommu.c | 54 ++++++++++++++++++++++++-------------
1 file changed, 35 insertions(+), 19 deletions(-)
--
2.43.0
next reply other threads:[~2025-05-09 6:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 14:00 Wei Wang [this message]
2025-05-09 14:00 ` [PATCH v1 1/3] iommu/vt-d: Eliminate pci_physfn() in dmar_find_matched_satc_unit() Wei Wang
2025-05-09 9:15 ` Yi Liu
2025-05-09 11:39 ` Wang, Wei W
2025-05-09 14:00 ` [PATCH v1 2/3] iommu/vt-d: Change dmar_ats_supported() to return boolean Wei Wang
2025-05-09 9:27 ` Yi Liu
2025-05-09 11:21 ` Wang, Wei W
2025-05-09 14:00 ` [PATCH v1 3/3] iommu/vt-d: Fix ATS support check for integrated endpoints Wei Wang
2025-05-09 9:32 ` Yi Liu
2025-05-09 11:12 ` Wang, Wei W
2025-05-12 2:43 ` Baolu Lu
2025-05-12 3:45 ` Wang, Wei W
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=20250509140021.4029303-1-wei.w.wang@intel.com \
--to=wei.w.wang@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=jroedel@suse.de \
--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
all inboxes | Powered by JetHome®