All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] [PULL REQUEST] Intel IOMMU updates for v6.16
Date: Fri, 16 May 2025 08:49:53 +0200	[thread overview]
Message-ID: <aCbgEdv-dMX7wa6G@8bytes.org> (raw)
In-Reply-To: <20250513030739.2718555-1-baolu.lu@linux.intel.com>

On Tue, May 13, 2025 at 11:07:34AM +0800, Lu Baolu wrote:
> Jason Gunthorpe (1):
>   iommu/vt-d: Restore WO permissions on second-level paging entries
> 
> Lu Baolu (2):
>   iommu/vt-d: Use ida to manage domain id
>   iommu/vt-d: Replace spin_lock with mutex to protect domain ida
> 
> Wei Wang (2):
>   iommu/vt-d: Eliminate pci_physfn() in dmar_find_matched_satc_unit()
>   iommu/vt-d: Change dmar_ats_supported() to return boolean
> 
>  drivers/iommu/intel/dmar.c  |   4 ++
>  drivers/iommu/intel/iommu.c | 113 ++++++++++--------------------------
>  drivers/iommu/intel/iommu.h |  21 +++++--
>  3 files changed, 51 insertions(+), 87 deletions(-)

Applied all, thanks Baolu.

      parent reply	other threads:[~2025-05-16  6:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13  3:07 [PATCH 0/5] [PULL REQUEST] Intel IOMMU updates for v6.16 Lu Baolu
2025-05-13  3:07 ` [PATCH 1/5] iommu/vt-d: Restore WO permissions on second-level paging entries Lu Baolu
2025-05-13  3:07 ` [PATCH 2/5] iommu/vt-d: Use ida to manage domain id Lu Baolu
2025-05-13  3:07 ` [PATCH 3/5] iommu/vt-d: Replace spin_lock with mutex to protect domain ida Lu Baolu
2025-05-13  3:07 ` [PATCH 4/5] iommu/vt-d: Eliminate pci_physfn() in dmar_find_matched_satc_unit() Lu Baolu
2025-05-13  3:07 ` [PATCH 5/5] iommu/vt-d: Change dmar_ats_supported() to return boolean Lu Baolu
2025-05-16  6:49 ` Joerg Roedel [this message]

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=aCbgEdv-dMX7wa6G@8bytes.org \
    --to=joro@8bytes.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --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.