From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Kan Liang <kan.liang@linux.intel.com>,
Lu Baolu <baolu.lu@linux.intel.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] [PULL REQUEST] iommu/vt-d: Fixes for v6.3-rc4
Date: Wed, 29 Mar 2023 21:47:18 +0800 [thread overview]
Message-ID: <20230329134721.469447-1-baolu.lu@linux.intel.com> (raw)
Hi Joerg,
Some fixes have been queued for v6.3. They aim to:
- Fix a lockdep splat
- Fix a supplement of the specification
- Fix a warning in perfmon code
This series is also available at github.
https://github.com/LuBaolu/intel-iommu/commits/vtd-fix-for-v6.3-rc4
Please consider them for the iommu/fix branch.
Best regards,
Lu Baolu
Kan Liang (1):
iommu/vt-d: Fix an IOMMU perfmon warning when CPU hotplug
Lu Baolu (2):
iommu/vt-d: Remove unnecessary locking in intel_irq_remapping_alloc()
iommu/vt-d: Allow zero SAGAW if second-stage not supported
include/linux/cpuhotplug.h | 1 -
drivers/iommu/intel/iommu.h | 2 +
drivers/iommu/intel/dmar.c | 3 +-
drivers/iommu/intel/irq_remapping.c | 6 ---
drivers/iommu/intel/perfmon.c | 68 +++++++++++++++++++----------
5 files changed, 48 insertions(+), 32 deletions(-)
--
2.34.1
next reply other threads:[~2023-03-29 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 13:47 Lu Baolu [this message]
2023-03-29 13:47 ` [PATCH 1/3] iommu/vt-d: Remove unnecessary locking in intel_irq_remapping_alloc() Lu Baolu
2023-03-29 13:47 ` [PATCH 2/3] iommu/vt-d: Allow zero SAGAW if second-stage not supported Lu Baolu
2023-03-29 13:47 ` [PATCH 3/3] iommu/vt-d: Fix an IOMMU perfmon warning when CPU hotplug Lu Baolu
2023-03-31 8:06 ` [PATCH 0/3] [PULL REQUEST] iommu/vt-d: Fixes for v6.3-rc4 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=20230329134721.469447-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
/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.