From: Keith Busch <kbusch@kernel.org>
To: Keith Busch <kbusch@meta.com>
Cc: linux-pci@vger.kernel.org, lukas@wunner.de, bhelgaas@google.com
Subject: Re: [PATCH 0/2] pcie hotplug and error fixes
Date: Wed, 12 Jun 2024 12:11:53 -0600 [thread overview]
Message-ID: <Zmnk6b_Y5FqENX7R@kbusch-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20240612181024.3577119-1-kbusch@meta.com>
On Wed, Jun 12, 2024 at 11:10:22AM -0700, Keith Busch wrote:
> 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
Oops, sorry for the noise here. I accidently pointed git send-email to
the wrong directory and resent v1 that was already flagged as breaking.
I'll resend the correct version shortly.
next prev parent reply other threads:[~2024-06-12 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 18:10 [PATCH 0/2] pcie hotplug and error fixes Keith Busch
2024-06-12 18:10 ` [PATCH 1/2] PCI: pciehp: fix concurrent sub-tree removal deadlock Keith Busch
2024-06-12 18:10 ` [PATCH 2/2] PCI: err: ensure stable topology during handling Keith Busch
2024-06-12 18:11 ` Keith Busch [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-10 22:03 [PATCH 0/2] pcie hotplug and error fixes 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=Zmnk6b_Y5FqENX7R@kbusch-mbp.dhcp.thefacebook.com \
--to=kbusch@kernel.org \
--cc=bhelgaas@google.com \
--cc=kbusch@meta.com \
--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