All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pranjal Shrivastava <praan@google.com>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: iommu@lists.linux.dev, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, Joerg Roedel <joro@8bytes.org>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	Ankit Soni <ankit.soni@amd.com>, Jason Gunthorpe <jgg@nvidia.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Samiullah Khawaja <skhawaja@google.com>
Subject: Re: [PATCH v3 0/5] iommu/amd: Refactors for ATS robustness
Date: Tue, 25 Aug 2026 10:37:09 +0000	[thread overview]
Message-ID: <ao1wVQzyCW22iNlQ@google.com> (raw)
In-Reply-To: <8e53fdee-2c3a-47c6-9478-19fbabef18eb@amd.com>

On Tue, Aug 25, 2026 at 12:36:18PM +0530, Vasant Hegde wrote:
> Pranjal,
> 
> 
> On 8/24/2026 5:53 PM, Pranjal Shrivastava wrote:
> > This series forms the second half of the subsystem-wide ATS robustness
> > updates. The first part (focusing on the core subsystem, Intel, and ARM
> > SMMUv3) has already been merged upstream [1]. This half addresses the
> > AMD IOMMU driver and standardizes the PCI ATS API.
> > 
> > In v2, the series has been significantly restructured based on feedback
> > on v1. 
> 
> Overall this looks good to me. We did run our CI w/ v2 and no regression found.
> 

Ack. v3 Just addressed a few comments. I'll send out a v4 based on the
feedback on this one soon.

Thanks,
Praan

      reply	other threads:[~2026-08-25 10:37 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 12:23 [PATCH v3 0/5] iommu/amd: Refactors for ATS robustness Pranjal Shrivastava
2026-08-24 12:23 ` [PATCH v3 1/5] iommu/amd: Refactor device probe and capability initialization Pranjal Shrivastava
2026-08-24 18:13   ` Jason Gunthorpe
2026-08-25 10:24     ` Pranjal Shrivastava
2026-08-25 11:50       ` Jason Gunthorpe
2026-08-25  6:59   ` Vasant Hegde
2026-08-25 10:25     ` Pranjal Shrivastava
2026-08-24 12:23 ` [PATCH v3 2/5] iommu/amd: Fix DTE clearing and rename iommu_ignore_device() Pranjal Shrivastava
2026-08-24 18:13   ` Jason Gunthorpe
2026-08-25 10:32     ` Pranjal Shrivastava
2026-08-25 11:49       ` Jason Gunthorpe
2026-08-25 17:29         ` Pranjal Shrivastava
2026-08-25 17:53           ` Jason Gunthorpe
2026-08-25 19:08             ` Pranjal Shrivastava
2026-08-26 11:28               ` Vasant Hegde
2026-08-26 12:21                 ` Jason Gunthorpe
2026-08-28  5:16                   ` Vasant Hegde
2026-08-28 11:53                     ` Jason Gunthorpe
2026-09-04 10:13                       ` Vasant Hegde
2026-09-04 14:25                         ` Jason Gunthorpe
2026-09-10 11:55                           ` Vasant Hegde
2026-09-10 13:47                             ` Pranjal Shrivastava
2026-09-10 14:15                               ` Vasant Hegde
2026-09-10 14:28                                 ` Pranjal Shrivastava
2026-08-24 21:47   ` Samiullah Khawaja
2026-08-25  7:01   ` Vasant Hegde
2026-08-24 12:23 ` [PATCH v3 3/5] iommu/amd: Split probe error paths to preserve IRQ remapping Pranjal Shrivastava
2026-08-24 18:13   ` Jason Gunthorpe
2026-08-25 10:34     ` Pranjal Shrivastava
2026-08-24 12:23 ` [PATCH v3 4/5] iommu/amd: Fail probe on ATS configuration failure Pranjal Shrivastava
2026-08-24 18:13   ` Jason Gunthorpe
2026-08-24 21:46   ` Samiullah Khawaja
2026-08-24 12:23 ` [PATCH v3 5/5] PCI/ATS: Mandate checking pci_ats_supported() before pci_prepare_ats() Pranjal Shrivastava
2026-08-24 18:13   ` Jason Gunthorpe
2026-08-24 18:13 ` [PATCH v3 0/5] iommu/amd: Refactors for ATS robustness Jason Gunthorpe
2026-08-25 10:39   ` Pranjal Shrivastava
2026-08-25 11:51     ` Jason Gunthorpe
2026-08-25  7:06 ` Vasant Hegde
2026-08-25 10:37   ` Pranjal Shrivastava [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=ao1wVQzyCW22iNlQ@google.com \
    --to=praan@google.com \
    --cc=ankit.soni@amd.com \
    --cc=bhelgaas@google.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=skhawaja@google.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=vasant.hegde@amd.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 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.