From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: mohd.syazwan.abdul.halim@intel.com,
Kunwu Chan <chentao@kylinos.cn>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/7] [PULL REQUEST] iommu/vt-d: Fixes for v6.7-rc3
Date: Wed, 22 Nov 2023 11:26:01 +0800 [thread overview]
Message-ID: <20231122032608.165144-1-baolu.lu@linux.intel.com> (raw)
Hi Joerg,
The following fixes have been queued for v6.7. They aim to:
- Do not support enforcing cache coherency for non-empty domains
- Avoid devTLB invalidation if iommu is off
- Disable PCI ATS in legacy passthrough mode
- Support non-PCI devices when clearing context
- Fix incorrect cache invalidation for mm notification
- Add MTL to quirk list to skip TE disabling
- Set variable intel_dirty_ops to static
Please consider them for the iommu/fix branch.
Best regards,
Lu Baolu
Abdul Halim, Mohd Syazwan (1):
iommu/vt-d: Add MTL to quirk list to skip TE disabling
Kunwu Chan (1):
iommu/vt-d: Set variable intel_dirty_ops to static
Lu Baolu (5):
iommu/vt-d: Support enforce_cache_coherency only for empty domains
iommu/vt-d: Omit devTLB invalidation requests when TES=0
iommu/vt-d: Disable PCI ATS in legacy passthrough mode
iommu/vt-d: Make context clearing consistent with context mapping
iommu/vt-d: Fix incorrect cache invalidation for mm notification
drivers/iommu/intel/iommu.h | 3 +++
drivers/iommu/intel/dmar.c | 18 ++++++++++++++++++
drivers/iommu/intel/iommu.c | 18 +++++++++++-------
drivers/iommu/intel/svm.c | 26 ++++++++++++++++++++++++++
4 files changed, 58 insertions(+), 7 deletions(-)
--
2.34.1
next reply other threads:[~2023-11-22 3:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 3:26 Lu Baolu [this message]
2023-11-22 3:26 ` [PATCH 1/7] iommu/vt-d: Support enforce_cache_coherency only for empty domains Lu Baolu
2023-11-22 3:26 ` [PATCH 2/7] iommu/vt-d: Omit devTLB invalidation requests when TES=0 Lu Baolu
2023-11-22 3:26 ` [PATCH 3/7] iommu/vt-d: Disable PCI ATS in legacy passthrough mode Lu Baolu
2023-11-22 3:26 ` [PATCH 4/7] iommu/vt-d: Make context clearing consistent with context mapping Lu Baolu
2023-11-22 3:26 ` [PATCH 5/7] iommu/vt-d: Add MTL to quirk list to skip TE disabling Lu Baolu
2023-11-22 3:26 ` [PATCH 6/7] iommu/vt-d: Fix incorrect cache invalidation for mm notification Lu Baolu
2023-11-22 3:26 ` [PATCH 7/7] iommu/vt-d: Set variable intel_dirty_ops to static Lu Baolu
2023-11-27 10:08 ` [PATCH 0/7] [PULL REQUEST] iommu/vt-d: Fixes for v6.7-rc3 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=20231122032608.165144-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=chentao@kylinos.cn \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mohd.syazwan.abdul.halim@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