mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolin Chen <nicolinc@nvidia.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: <joro@8bytes.org>, <will@kernel.org>, <robin.murphy@arm.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>, <lenb@kernel.org>,
	<bhelgaas@google.com>, <alex@shazbot.org>, <jgg@nvidia.com>,
	<kevin.tian@intel.com>, <baolu.lu@linux.intel.com>,
	<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
	<linux-pci@vger.kernel.org>, <kvm@vger.kernel.org>,
	<patches@lists.linux.dev>, <pjaroszynski@nvidia.com>,
	<vsethi@nvidia.com>, <etzhao1900@gmail.com>,
	Danny Gonzalez <digonzal@google.com>
Subject: Re: [PATCH v8 5/5] PCI: Suspend iommu function prior to resetting a device
Date: Wed, 4 Nov 2026 16:03:22 -0800	[thread overview]
Message-ID: <auvHyrZmMXLTFyz9@nvidia.com> (raw)
In-Reply-To: <20261104235238.GA1469671@bhelgaas>

On Wed, Nov 04, 2026 at 05:55:00PM -0600, Bjorn Helgaas wrote:
> On Mon, Dec 15, 2025 at 01:42:20PM -0800, Nicolin Chen wrote:
> > @@ -4885,10 +4919,20 @@ static int pci_reset_bus_function(struct pci_dev *dev, bool probe)
> >  		return -ENOTTY;
> >  	}
> >  
> > +	rc = pci_dev_reset_iommu_prepare(dev);
> > +	if (rc) {
> > +		pci_err(dev, "failed to stop IOMMU for a PCI reset: %d\n", rc);
> > +		return rc;
> > +	}
> 
> Unlike the other reset functions, this one calls
> pci_dev_reset_iommu_prepare() even when probe==true, i.e., we don't
> want to actually perform the reset, we just want to know whether the
> reset method might work.
> 
> It's at least unnecessary to call pci_dev_reset_iommu_prepare() and
> pci_dev_reset_iommu_done() in that case, and maybe even problematic
> because the pci_init_reset_methods() probe happens from
> pci_init_capabilities(), which is pretty early during PCI enumeration
> of the device.
> 
> I know this has already been merged as f5b16b802174 ("PCI: Suspend
> iommu function prior to resetting a device"), and I'm not sure whether
> we should do anything about it.  I wonder if we should just skip the
> prepare/done when probe==true?

I've posted a fix for a few times actually. The latest one was
posted yesterday after a split:
https://lore.kernel.org/linux-iommu/c66d5221a8e4356316d4f614c8584a80dc9d71b6.1793729707.git.nicolinc@nvidia.com/

Please help review it (and the other PCI patch) as well.

Thanks
Nicolin

  reply	other threads:[~2026-11-05  0:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 21:42 [PATCH v8 0/5] Disable ATS via iommu during PCI resets Nicolin Chen
2025-12-15 21:42 ` [PATCH v8 1/5] iommu: Lock group->mutex in iommu_deferred_attach() Nicolin Chen
2025-12-16  1:14   ` Samiullah Khawaja
2025-12-15 21:42 ` [PATCH v8 2/5] iommu: Tidy domain for iommu_setup_dma_ops() Nicolin Chen
2025-12-15 21:42 ` [PATCH v8 3/5] iommu: Add iommu_driver_get_domain_for_dev() helper Nicolin Chen
2025-12-15 21:42 ` [PATCH v8 4/5] iommu: Introduce pci_dev_reset_iommu_prepare/done() Nicolin Chen
2025-12-15 21:42 ` [PATCH v8 5/5] PCI: Suspend iommu function prior to resetting a device Nicolin Chen
2026-11-04 23:55   ` Bjorn Helgaas
2026-11-05  0:03     ` Nicolin Chen [this message]
2026-11-05  0:13       ` Bjorn Helgaas
2026-11-05  1:12         ` Nicolin Chen
2026-01-10  9:27 ` [PATCH v8 0/5] Disable ATS via iommu during PCI resets Jörg Rödel

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=auvHyrZmMXLTFyz9@nvidia.com \
    --to=nicolinc@nvidia.com \
    --cc=alex@shazbot.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=digonzal@google.com \
    --cc=etzhao1900@gmail.com \
    --cc=helgaas@kernel.org \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=pjaroszynski@nvidia.com \
    --cc=rafael@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=vsethi@nvidia.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®