All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
	linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: [git pull] IOMMU Fixes for Linux v6.14-rc4
Date: Fri, 28 Feb 2025 16:58:07 +0100	[thread overview]
Message-ID: <Z8HdD3MdUViUc0eo@8bytes.org> (raw)

Hi Linus,

The following changes since commit d082ecbc71e9e0bf49883ee4afd435a77a5101b6:

  Linux 6.14-rc4 (2025-02-23 12:32:57 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/iommu/linux.git tags/iommu-fixes-v6.14-rc4

for you to fetch changes up to b150654f74bf0df8e6a7936d5ec51400d9ec06d8:

  iommu/vt-d: Fix suspicious RCU usage (2025-02-28 12:19:01 +0100)

----------------------------------------------------------------
IOMMU Fixes for Linux v6.14-rc4:

Including:

	- Intel VT-d fixes:
	  - Fix suspicious RCU usage splat.
	  - Fix passthrough for devices under PCIe-PCI bridge.

	- AMD-Vi fix:
	  - Fix to preserve bits when updating device table entries.

----------------------------------------------------------------
Alejandro Jimenez (1):
      iommu/amd: Preserve default DTE fields when updating Host Page Table Root

Jerry Snitselaar (1):
      iommu/vt-d: Remove device comparison in context_setup_pass_through_cb

Lu Baolu (1):
      iommu/vt-d: Fix suspicious RCU usage

 drivers/iommu/amd/iommu.c   |  4 ++--
 drivers/iommu/intel/dmar.c  |  1 +
 drivers/iommu/intel/iommu.c | 10 +++++++---
 3 files changed, 10 insertions(+), 5 deletions(-)

Please pull.

Thanks,

	Joerg

             reply	other threads:[~2025-02-28 15:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 15:58 Joerg Roedel [this message]
2025-03-01  0:08 ` [git pull] IOMMU Fixes for Linux v6.14-rc4 pr-tracker-bot

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=Z8HdD3MdUViUc0eo@8bytes.org \
    --to=joro@8bytes.org \
    --cc=iommu@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=will@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.