From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Kevin Tian <kevin.tian@intel.com>,
Lennert Buytenhek <buytenh@wantstofly.org>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Jerry Snitselaar <jsnitsel@redhat.com>,
Wen Jin <wen.jin@intel.com>,
iommu@lists.linux.dev, iommu@lists.linux-foundation.org
Subject: [PATCH 0/4] iommu/vt-d: Fixes for v6.0-rc3
Date: Tue, 23 Aug 2022 14:15:53 +0800 [thread overview]
Message-ID: <20220823061557.1631056-1-baolu.lu@linux.intel.com> (raw)
Hi Joerg,
Below fixes are queued for v6.0-rc3. They aim to fix:
- Boot kdump kernels with VT-d scalable mode on
- Calculate the right page table levels
- Fix a recursive lock issue
- Fix a lockdep splat issue
Please consider it for the iommu/fix branch.
Best regards,
Lu Baolu
Lu Baolu (4):
iommu/vt-d: Fix kdump kernels boot failure with scalable mode
iommu/vt-d: Correctly calculate sagaw value of IOMMU
iommu/vt-d: Fix recursive lock issue in iommu_flush_dev_iotlb()
iommu/vt-d: Fix lockdep splat due to klist iteration in atomic context
drivers/iommu/intel/iommu.h | 9 +-
drivers/iommu/intel/iommu.c | 214 +++++++++++++++++++-----------------
2 files changed, 117 insertions(+), 106 deletions(-)
--
2.25.1
next reply other threads:[~2022-08-23 6:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 6:15 Lu Baolu [this message]
2022-08-23 6:15 ` [PATCH 1/4] iommu/vt-d: Fix kdump kernels boot failure with scalable mode Lu Baolu
2022-08-23 6:15 ` [PATCH 2/4] iommu/vt-d: Correctly calculate sagaw value of IOMMU Lu Baolu
2022-08-23 6:15 ` [PATCH 3/4] iommu/vt-d: Fix recursive lock issue in iommu_flush_dev_iotlb() Lu Baolu
2022-08-23 6:15 ` [PATCH 4/4] iommu/vt-d: Fix lockdep splat due to klist iteration in atomic context Lu Baolu
2022-09-07 13:15 ` [PATCH 0/4] iommu/vt-d: Fixes for v6.0-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=20220823061557.1631056-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=buytenh@wantstofly.org \
--cc=iommu@lists.linux-foundation.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=jsnitsel@redhat.com \
--cc=kevin.tian@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=wen.jin@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