From: Bjorn Helgaas <helgaas@kernel.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: Laurent Bigonville <bigon@bigon.be>,
Mario Limonciello <mario.limonciello@amd.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Mika Westerberg <westeri@kernel.org>,
Alan Borzeszkowski <alan.borzeszkowski@linux.intel.com>,
Gil Fine <gil.fine@linux.intel.com>,
Rene Sapiens <rene.sapiens@intel.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 0/5] PCI: Clean up and fix is_hotplug_bridge usage
Date: Tue, 22 Jul 2025 17:35:22 -0500 [thread overview]
Message-ID: <20250722223522.GA2856849@bhelgaas> (raw)
In-Reply-To: <cover.1752390101.git.lukas@wunner.de>
On Sun, Jul 13, 2025 at 04:31:00PM +0200, Lukas Wunner wrote:
> The original impetus of this series is to fix a runtime PM ref imbalance
> on hot-removal of PCIe hotplug ports (patch [1/5]).
>
> That is achieved by adding an is_pciehp flag to struct pci_dev.
> The new flag is only set on PCIe Hot-Plug Capable ports, unlike the
> existing is_hotplug_bridge flag, which is also set on ACPI slots and
> Conventional PCI hotplug bridges (via quirk_hotplug_bridge()).
>
> Patches [2/5] to [4/5] replace is_hotplug_bridge with is_pciehp in a
> number of places for clarity and to fix some actual bugs.
>
> Optional patch [5/5] follows a suggestion from Bjorn to set
> host->native_pcie_hotplug up front based on pcie_ports_native.
> That patch needs an ack from Rafael because it touches ACPI code.
> Up to Bjorn whether it is a worthwhile improvement or not.
>
> I'm open to suggestions for a different name than is_pciehp,
> e.g. is_pciehp_bridge.
>
> I've reviewed this a couple of times, but would appreciate further
> reviewing and testing by others to raise the confidence. Mika is
> out of office until July 28, so I'm cc'ing thunderbolt developers
> Alan, Gil and Rene.
>
> I've got an additional patch to replace is_hotplug_bridge with is_pciehp
> in quirk_thunderbolt_hotplug_msi() and tb_apple_add_links(). I intend
> to submit it to Mika separately if/when this series is accepted.
>
> Link to v1, which consisted only of a (problematic) variant of patch [1/5]:
> https://lore.kernel.org/r/86c3bd52bda4552d63ffb48f8a30343167e85271.1750698221.git.lukas@wunner.de/
>
> Lukas Wunner (5):
> PCI/ACPI: Fix runtime PM ref imbalance on Hot-Plug Capable ports
> PCI/portdrv: Use is_pciehp instead of is_hotplug_bridge
> PCI: pciehp: Use is_pciehp instead of is_hotplug_bridge
> PCI: Move is_pciehp check out of pciehp_is_native()
> PCI: Set native_pcie_hotplug up front based on pcie_ports_native
>
> drivers/acpi/pci_root.c | 3 ++-
> drivers/pci/hotplug/pciehp_hpc.c | 2 +-
> drivers/pci/pci-acpi.c | 10 +---------
> drivers/pci/pci.c | 18 +++++++++++++-----
> drivers/pci/pcie/portdrv.c | 4 ++--
> drivers/pci/probe.c | 2 +-
> include/linux/pci.h | 6 ++++++
> include/linux/pci_hotplug.h | 3 ++-
> 8 files changed, 28 insertions(+), 20 deletions(-)
Thanks! I applied these to pci/hotplug, hoping to put them in v6.17.
I moved the previous pci/hotplug branch to pci/hotplug-pnv_php.
next prev parent reply other threads:[~2025-07-22 22:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-13 14:31 [PATCH v2 0/5] PCI: Clean up and fix is_hotplug_bridge usage Lukas Wunner
2025-07-13 14:31 ` [PATCH v2 1/5] PCI/ACPI: Fix runtime PM ref imbalance on Hot-Plug Capable ports Lukas Wunner
2025-07-26 20:50 ` Rafael J. Wysocki
2025-07-13 14:31 ` [PATCH v2 2/5] PCI/portdrv: Use is_pciehp instead of is_hotplug_bridge Lukas Wunner
2025-07-13 14:31 ` [PATCH v2 3/5] PCI: pciehp: " Lukas Wunner
2025-07-13 14:31 ` [PATCH v2 4/5] PCI: Move is_pciehp check out of pciehp_is_native() Lukas Wunner
2025-07-13 14:31 ` [PATCH v2 5/5] PCI: Set native_pcie_hotplug up front based on pcie_ports_native Lukas Wunner
2025-07-14 23:00 ` Sathyanarayanan Kuppuswamy
2025-07-14 23:50 ` Sathyanarayanan Kuppuswamy
2025-07-22 22:33 ` Bjorn Helgaas
2025-07-22 22:35 ` Bjorn Helgaas [this message]
2025-07-25 8:19 ` [PATCH v2 0/5] PCI: Clean up and fix is_hotplug_bridge usage Lukas Wunner
2025-07-25 19:33 ` Bjorn Helgaas
2025-07-26 20:52 ` Rafael J. Wysocki
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=20250722223522.GA2856849@bhelgaas \
--to=helgaas@kernel.org \
--cc=alan.borzeszkowski@linux.intel.com \
--cc=bigon@bigon.be \
--cc=gil.fine@linux.intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mario.limonciello@amd.com \
--cc=rafael@kernel.org \
--cc=rene.sapiens@intel.com \
--cc=westeri@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;
as well as URLs for NNTP newsgroup(s).