From: Bjorn Helgaas <helgaas@kernel.org>
To: David Matlack <dmatlack@google.com>
Cc: kexec@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-pci@vger.kernel.org,
Adithya Jayachandran <ajayachandra@nvidia.com>,
Alexander Graf <graf@amazon.com>,
Alex Williamson <alex@shazbot.org>,
Bjorn Helgaas <bhelgaas@google.com>, Chris Li <chrisl@kernel.org>,
David Rientjes <rientjes@google.com>,
Jacob Pan <jacob.pan@linux.microsoft.com>,
Jason Gunthorpe <jgg@nvidia.com>,
Jonathan Corbet <corbet@lwn.net>, Josh Hilke <jrhilke@google.com>,
Leon Romanovsky <leonro@nvidia.com>,
Lukas Wunner <lukas@wunner.de>, Mike Rapoport <rppt@kernel.org>,
Parav Pandit <parav@nvidia.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pranjal Shrivastava <praan@google.com>,
Pratyush Yadav <pratyush@kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>,
Samiullah Khawaja <skhawaja@google.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Vipin Sharma <vipinsh@google.com>, William Tu <witu@nvidia.com>,
Yi Liu <yi.l.liu@intel.com>
Subject: Re: [PATCH v8 06/12] PCI: liveupdate: Auto-preserve upstream bridges across Live Update
Date: Wed, 16 Sep 2026 19:07:23 -0500 [thread overview]
Message-ID: <20260917000723.GA992337@bhelgaas> (raw)
In-Reply-To: <20260728221007.2098560-7-dmatlack@google.com>
On Tue, Jul 28, 2026 at 10:10:00PM +0000, David Matlack wrote:
> When a PCI device is preserved across a Live Update, all of its upstream
> bridges up to the root port must also be preserved. This enables the PCI
> core and any drivers bound to the bridges to manage bridges correctly
> across a Live Update.
>
> Notably, this will be used in subsequent commits to ensure that
> preserved devices can continue performing memory transactions without a
> disruption or change in routing.
>
> To preserve bridges, the PCI core tracks the number of downstream
> devices preserved under each bridge using a reference count in struct
> pci_dev_ser. This allows a bridge to remain preserved until all its
> downstream preserved devices are unpreserved or finish their
> participation in the Live Update.
> ...
> +static int pci_liveupdate_unpreserve_device(struct pci_flb_outgoing *outgoing,
> + struct pci_dev *dev)
> {
> struct pci_dev_ser *dev_ser = dev->liveupdate.outgoing;
>
> if (!dev_ser) {
> pci_warn(dev, "Cannot unpreserve device that is not preserved\n");
> - return;
> + return -EINVAL;
> + }
> +
> + if (!dev_ser->refcount) {
> + pci_WARN(dev, 1, "Preserved device has a 0 refcount!\n");
> + return -EINVAL;
> }
>
> + if (--dev_ser->refcount)
> + return 0;
I guess this is a nit: I was looking for a dev_ser->refcount++ in this
patch to correspond with this decrement. I *guess* the
"dev_ser->refcount = 1" in pci_liveupdate_preserve_device() starts
that, and the "dev->liveupdate.outgoing->refcount++" there is an
increment of the same refcount? The connections there don't seem
quite obvious to me.
But I guess "dev_ser->refcount = 1" was added by a different patch, so
probably *not* the same?
> pci_info(dev, "Device will no longer be preserved across next Live Update\n");
> outgoing->ser->nr_devices--;
> memset(dev_ser, 0, sizeof(*dev_ser));
> dev->liveupdate.outgoing = NULL;
> + return 0;
> +}
> @@ -385,13 +418,23 @@ static int pci_liveupdate_preserve_device(struct pci_flb_outgoing *outgoing,
> }
>
> if (dev->liveupdate.outgoing) {
> - pci_warn(dev, "Device is already preserved\n");
> - return -EBUSY;
> - }
> + if (!dev->liveupdate.outgoing->refcount) {
> + pci_WARN(dev, 1, "Preserved device with 0 refcount!\n");
> + return -EINVAL;
> + }
>
> - if (!pci_is_root_bus(dev->bus)) {
> - pci_warn(dev, "Cannot preserve devices behind bridges\n");
> - return -EINVAL;
> + /*
> + * Endpoint devices should not be preserved more than once.
> + * Bridges are preserved once for every downstream device that
> + * is preserved.
> + */
> + if (!dev->subordinate) {
> + pci_warn(dev, "Device is already preserved\n");
> + return -EBUSY;
> + }
> +
> + dev->liveupdate.outgoing->refcount++;
> + return 0;
> }
>
> dev_ser = pci_flb_alloc_dev_ser(outgoing);
next prev parent reply other threads:[~2026-09-17 0:07 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 22:09 [PATCH v8 00/12] PCI: liveupdate: PCI core support for " David Matlack
2026-07-28 22:09 ` [PATCH v8 01/12] PCI: liveupdate: Set up FLB handler for the PCI core David Matlack
2026-08-17 21:12 ` Samiullah Khawaja
2026-09-10 23:48 ` Bjorn Helgaas
2026-09-11 16:44 ` David Matlack
2026-09-16 23:50 ` Bjorn Helgaas
2026-09-18 0:48 ` David Matlack
2026-07-28 22:09 ` [PATCH v8 02/12] PCI: liveupdate: Track outgoing preserved PCI devices David Matlack
2026-08-24 20:14 ` Samiullah Khawaja
2026-08-27 21:47 ` Bjorn Helgaas
2026-09-16 3:10 ` Zhu Yanjun
2026-09-16 14:58 ` David Matlack
2026-07-28 22:09 ` [PATCH v8 03/12] PCI: liveupdate: Track incoming " David Matlack
2026-08-24 20:13 ` Samiullah Khawaja
2026-09-10 23:49 ` Bjorn Helgaas
2026-09-11 16:45 ` David Matlack
2026-09-16 3:31 ` Zhu Yanjun
2026-09-16 17:28 ` David Matlack
2026-09-16 18:25 ` Pratyush Yadav
2026-09-16 18:31 ` David Matlack
2026-09-16 18:58 ` Pratyush Yadav
2026-09-16 19:23 ` David Matlack
2026-07-28 22:09 ` [PATCH v8 04/12] PCI: liveupdate: Document driver binding responsibilities David Matlack
2026-09-10 23:50 ` Bjorn Helgaas
2026-07-28 22:09 ` [PATCH v8 05/12] PCI: liveupdate: Preserve bus numbers during Live Update David Matlack
2026-09-10 23:51 ` Bjorn Helgaas
2026-09-11 18:30 ` David Matlack
2026-09-12 17:31 ` David Matlack
2026-09-16 23:54 ` Bjorn Helgaas
2026-07-28 22:10 ` [PATCH v8 06/12] PCI: liveupdate: Auto-preserve upstream bridges across " David Matlack
2026-08-24 13:41 ` Pranjal Shrivastava
2026-09-10 23:51 ` Bjorn Helgaas
2026-09-11 17:00 ` David Matlack
2026-09-17 0:18 ` Bjorn Helgaas
2026-09-17 23:42 ` David Matlack
2026-09-17 0:07 ` Bjorn Helgaas [this message]
2026-09-17 23:44 ` David Matlack
2026-07-28 22:10 ` [PATCH v8 07/12] PCI: Refactor matching logic for pci_dev_acs_ops David Matlack
2026-07-28 22:10 ` [PATCH v8 08/12] PCI: liveupdate: Adopt ACS controls in incoming preserved devices David Matlack
2026-08-24 13:42 ` Pranjal Shrivastava
2026-09-10 23:51 ` Bjorn Helgaas
2026-09-11 18:31 ` David Matlack
2026-09-14 16:45 ` David Matlack
2026-09-17 0:23 ` Bjorn Helgaas
2026-07-28 22:10 ` [PATCH v8 09/12] PCI: liveupdate: Adopt ARI Forwarding Enable on preserved bridges David Matlack
2026-08-24 13:43 ` Pranjal Shrivastava
2026-09-17 19:47 ` Bjorn Helgaas
2026-07-28 22:10 ` [PATCH v8 10/12] PCI: liveupdate: Freeze preservation status during shutdown David Matlack
2026-08-24 20:07 ` Samiullah Khawaja
2026-09-17 20:17 ` Bjorn Helgaas
2026-09-17 23:38 ` David Matlack
2026-07-28 22:10 ` [PATCH v8 11/12] PCI: liveupdate: Do not disable bus mastering on preserved devices during kexec David Matlack
2026-08-24 20:02 ` Samiullah Khawaja
2026-09-17 20:19 ` Bjorn Helgaas
2026-07-28 22:10 ` [PATCH v8 12/12] Documentation: PCI: Add documentation for Live Update David Matlack
2026-08-24 20:01 ` Samiullah Khawaja
2026-09-17 21:39 ` Bjorn Helgaas
2026-09-17 23:33 ` David Matlack
2026-08-18 17:01 ` [PATCH v8 00/12] PCI: liveupdate: PCI core support " David Matlack
2026-09-10 21:37 ` Pasha Tatashin
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=20260917000723.GA992337@bhelgaas \
--to=helgaas@kernel.org \
--cc=ajayachandra@nvidia.com \
--cc=alex@shazbot.org \
--cc=bhelgaas@google.com \
--cc=chrisl@kernel.org \
--cc=corbet@lwn.net \
--cc=dmatlack@google.com \
--cc=graf@amazon.com \
--cc=jacob.pan@linux.microsoft.com \
--cc=jgg@nvidia.com \
--cc=jrhilke@google.com \
--cc=kexec@lists.infradead.org \
--cc=leonro@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=parav@nvidia.com \
--cc=pasha.tatashin@soleen.com \
--cc=praan@google.com \
--cc=pratyush@kernel.org \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=saeedm@nvidia.com \
--cc=skhan@linuxfoundation.org \
--cc=skhawaja@google.com \
--cc=vipinsh@google.com \
--cc=witu@nvidia.com \
--cc=yi.l.liu@intel.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
all inboxes | Powered by JetHome®