Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Pranjal Shrivastava <praan@google.com>
To: bhelgaas@google.com, linux-pci@vger.kernel.org
Cc: linux-iommu@vger.kernel.org, joerg.roedel@amd.com,
	vasant.hegde@amd.com,  baolu.lu@linux.intel.com,
	nicolinc@nvidia.com, jgg@nvidia.com,  skhawaja@google.com,
	Pranjal Shrivastava <praan@google.com>
Subject: [PATCH v4 0/1] PCI/ATS: Mandate checking pci_ats_supported() before pci_prepare_ats()
Date: Thu,  1 Oct 2026 23:33:37 +0000	[thread overview]
Message-ID: <20261001233338.918408-1-praan@google.com> (raw)

Hi Bjorn,

This single-patch submission represents the final core enforcement for the 
PCIe ATS robustness hardening effort.

This work was split into two parallel driver-specific consolidation series:
 1. Intel & ARM [1]
 2. AMD [2]

All the prerequisite driver refactors from both series have now been 
merged into the IOMMU tree by Joerg, with the latest merge commit [3].

As the driver-side safety checks are now fully in place, Joerg 
requested [4] that this final, PCI core patch be submitted through the
PCIe tree. Hence, I'm sending this as a standalone patch rebased on the
pci tree (for-next branch).

Thanks,
Praan

[1] https://lore.kernel.org/all/20260615235037.259909-1-praan@google.com/
[2] https://lore.kernel.org/all/20260910142655.3281464-1-praan@google.com/
[3] https://git.kernel.org/pub/scm/linux/kernel/git/iommu/linux.git/commit/?id=622384f54a8415f28bf7cf11cda95ab125488ca1
[4] https://lore.kernel.org/all/arUOoLwpfNlIvIXy@8bytes.org/

Pranjal Shrivastava (1):
  PCI/ATS: Mandate checking pci_ats_supported() before pci_prepare_ats()

 drivers/pci/ats.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

-- 
2.56.0.rc1.315.gc6ed9934b7-goog


             reply	other threads:[~2026-10-01 23:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 23:33 Pranjal Shrivastava [this message]
2026-10-01 23:33 ` [PATCH v4 1/1] PCI/ATS: Mandate checking pci_ats_supported() before pci_prepare_ats() Pranjal Shrivastava
2026-10-02  9:14   ` sashiko-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=20261001233338.918408-1-praan@google.com \
    --to=praan@google.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=jgg@nvidia.com \
    --cc=joerg.roedel@amd.com \
    --cc=linux-iommu@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=skhawaja@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox