From: Keith Busch <kbusch@meta.com>
To: <linux-pci@vger.kernel.org>, <lukas@wunner.de>, <bhelgaas@google.com>
Cc: Keith Busch <kbusch@kernel.org>
Subject: [PATCH 0/2] pcie hotplug and error fixes
Date: Mon, 10 Jun 2024 15:03:01 -0700 [thread overview]
Message-ID: <20240610220304.3162895-1-kbusch@meta.com> (raw)
From: Keith Busch <kbusch@kernel.org>
I am working with larger pcie topologies again, and we're seeing some
failures when dealing with certain overlapping pcie events.
The topology is essentially this:
[Root Port] <-> [UpStream Port] <-> [DownStream Port] <-> [End Device]
An error between the DSP and ED triggers DPC. There's only inband
presence detection so it also triggers hotplug. Before the error
handling is completed, though, another error seen by the RP triggers its
own DPC handling.
The concurrent event handling reveals some interesting races, and this
small patchset tries to address these in the low invasive way.
Keith Busch (2):
PCI: pciehp: fix concurrent sub-tree removal deadlock
PCI: err: ensure stable topology during handling
drivers/pci/hotplug/pciehp_pci.c | 12 +++++++++---
drivers/pci/pci.h | 1 +
drivers/pci/pcie/err.c | 8 +++++++-
drivers/pci/probe.c | 24 ++++++++++++++++++++++++
include/linux/pci.h | 2 ++
5 files changed, 43 insertions(+), 4 deletions(-)
--
2.43.0
next reply other threads:[~2024-06-10 22:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 22:03 Keith Busch [this message]
2024-06-10 22:03 ` [PATCH 1/2] PCI: pciehp: fix concurrent sub-tree removal deadlock Keith Busch
2024-06-11 6:19 ` kernel test robot
2024-06-11 6:19 ` kernel test robot
2024-06-11 14:33 ` Keith Busch
2024-06-10 22:03 ` [PATCH 2/2] PCI: err: ensure stable topology during handling Keith Busch
-- strict thread matches above, loose matches on Subject: below --
2024-06-12 18:10 [PATCH 0/2] pcie hotplug and error fixes Keith Busch
2024-06-12 18:11 ` Keith Busch
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=20240610220304.3162895-1-kbusch@meta.com \
--to=kbusch@meta.com \
--cc=bhelgaas@google.com \
--cc=kbusch@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
/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