Linux IOMMU Development
 help / color / mirror / Atom feed
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] [PULL REQUEST] iommu/vt-d: Fixes for v6.15-rc1
Date: Wed, 19 Mar 2025 10:20:58 +0800	[thread overview]
Message-ID: <20250319022101.1053133-1-baolu.lu@linux.intel.com> (raw)

Hi Joerg,

The following fixes have been queued for the Intel iommu driver. They
aim to solve the following issues:

- Fix a lockdep warning of possible circular locking dependency
- Prevent disabled posted MSIs when IRTE reverts from vCPU to host

These fixes are non-critical for v6.14-rc. Considering the upcoming
merge window, it would be fine to include them with other patches for
v6.15.

Can you please take them?

Best regards,
baolu

Lu Baolu (1):
  iommu/vt-d: Fix possible circular locking dependency

Sean Christopherson (2):
  iommu/vt-d: Put IRTE back into posted MSI mode if vCPU posting is
    disabled
  iommu/vt-d: Don't clobber posted vCPU IRTE when host IRQ affinity
    changes

 drivers/iommu/intel/iommu.c         |  2 ++
 drivers/iommu/intel/irq_remapping.c | 42 ++++++++++++++++++-----------
 2 files changed, 29 insertions(+), 15 deletions(-)

-- 
2.43.0


             reply	other threads:[~2025-03-19  2:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19  2:20 Lu Baolu [this message]
2025-03-19  2:20 ` [PATCH 1/3] iommu/vt-d: Put IRTE back into posted MSI mode if vCPU posting is disabled Lu Baolu
2025-03-19  2:21 ` [PATCH 2/3] iommu/vt-d: Don't clobber posted vCPU IRTE when host IRQ affinity changes Lu Baolu
2025-03-19  2:21 ` [PATCH 3/3] iommu/vt-d: Fix possible circular locking dependency Lu Baolu
2025-03-20  8:04 ` [PATCH 0/3] [PULL REQUEST] iommu/vt-d: Fixes for v6.15-rc1 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=20250319022101.1053133-1-baolu.lu@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox