public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Nicolin Chen <nicolinc@nvidia•com>
To: Pranjal Shrivastava <praan@google•com>
Cc: <iommu@lists•linux.dev>, <linux-pci@vger•kernel.org>,
	<linux-arm-kernel@lists•infradead.org>,
	<linux-kernel@vger•kernel.org>, "Joerg Roedel" <joro@8bytes•org>,
	Will Deacon <will@kernel•org>,
	Bjorn Helgaas <bhelgaas@google•com>,
	David Woodhouse <dwmw2@infradead•org>,
	Lu Baolu <baolu.lu@linux•intel.com>,
	Robin Murphy <robin.murphy@arm•com>,
	"Suravee Suthikulpanit" <suravee.suthikulpanit@amd•com>,
	Jason Gunthorpe <jgg@ziepe•ca>,
	David Matlack <dmatlack@google•com>,
	Samiullah Khawaja <skhawaja@google•com>,
	Daniel Mentz <danielmentz@google•com>,
	Pasha Tatashin <pasha.tatashin@soleen•com>,
	Mostafa Saleh <smostafa@google•com>,
	"Jason Gunthorpe" <jgg@nvidia•com>
Subject: Re: [PATCH v4 1/5] PCI/ATS: Ensure pci_ats_supported() is PF-aware for VFs
Date: Mon, 25 May 2026 12:42:21 -0700	[thread overview]
Message-ID: <ahSmHVGOUQDd2bkk@Asurada-Nvidia> (raw)
In-Reply-To: <20260525184347.4059549-2-praan@google.com>

On Mon, May 25, 2026 at 06:43:43PM +0000, Pranjal Shrivastava wrote:
> Update pci_ats_supported() to additionally check the associated PF's
> status when called on a VF. This ensures that PF-level quirks and
> untrusted status are correctly propagated to VFs, providing a robust
> support check that aligns with the kernel's PF-centric ATS configuration
> model and is immune to the timing of VF-specific fixups.
> 
> Reviewed-by: Jason Gunthorpe <jgg@nvidia•com>
> Reviewed-by: Samiullah Khawaja <skhawaja@google•com>
> Signed-off-by: Pranjal Shrivastava <praan@google•com>

Reviewed-by: Nicolin Chen <nicolinc@nvidia•com>


  reply	other threads:[~2026-05-25 20:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25 18:43 [PATCH v4 0/5] iommu: Standardize ATS robustness and state tracking Pranjal Shrivastava
2026-05-25 18:43 ` [PATCH v4 1/5] PCI/ATS: Ensure pci_ats_supported() is PF-aware for VFs Pranjal Shrivastava
2026-05-25 19:42   ` Nicolin Chen [this message]
2026-05-25 18:43 ` [PATCH v4 2/5] PCI/ATS: Validate STU for VFs in pci_prepare_ats() Pranjal Shrivastava
2026-05-25 19:46   ` Nicolin Chen
2026-05-28 20:27     ` Pranjal Shrivastava
2026-05-25 18:43 ` [PATCH v4 3/5] iommu/arm-smmu-v3: Fix ATS state tracking Pranjal Shrivastava
2026-05-25 20:05   ` Nicolin Chen
2026-05-25 20:30     ` Pranjal Shrivastava
2026-05-25 20:40       ` Nicolin Chen
2026-05-25 18:43 ` [PATCH v4 4/5] iommu/vt-d: Fail probe on ATS configuration failure Pranjal Shrivastava
2026-05-25 18:43 ` [PATCH v4 5/5] iommu/amd: " Pranjal Shrivastava

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=ahSmHVGOUQDd2bkk@Asurada-Nvidia \
    --to=nicolinc@nvidia$(echo .)com \
    --cc=baolu.lu@linux$(echo .)intel.com \
    --cc=bhelgaas@google$(echo .)com \
    --cc=danielmentz@google$(echo .)com \
    --cc=dmatlack@google$(echo .)com \
    --cc=dwmw2@infradead$(echo .)org \
    --cc=iommu@lists$(echo .)linux.dev \
    --cc=jgg@nvidia$(echo .)com \
    --cc=jgg@ziepe$(echo .)ca \
    --cc=joro@8bytes$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-pci@vger$(echo .)kernel.org \
    --cc=pasha.tatashin@soleen$(echo .)com \
    --cc=praan@google$(echo .)com \
    --cc=robin.murphy@arm$(echo .)com \
    --cc=skhawaja@google$(echo .)com \
    --cc=smostafa@google$(echo .)com \
    --cc=suravee.suthikulpanit@amd$(echo .)com \
    --cc=will@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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