From: Lukas Wunner <lukas@wunner.de>
To: Niklas Cassel <cassel@kernel.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Wilfred Mallawa <wilfred.mallawa@wdc.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Damien Le Moal <dlemoal@kernel.org>,
linux-pci@vger.kernel.org
Subject: Re: reset_slot() callback not respecting MPS config
Date: Fri, 23 May 2025 16:59:08 +0200 [thread overview]
Message-ID: <aDCNPFBwHSPe9WLi@wunner.de> (raw)
In-Reply-To: <aDAdjie1jGBQ-mKf@ryzen>
On Fri, May 23, 2025 at 09:02:38AM +0200, Niklas Cassel wrote:
> I kind of liked the earlier revision of Mani's series where we kicked the
> devices off the bus, that way, we would re-use the exact same code paths
> as when doing the initial enumeration.
>
> Also, by removing the device, the exact same solution works fine both for
> link-down (since the device might never come back again), and for a sysfs
> initiated reset.
PCI drivers such as NVMe are capable of recovering gracefully from reset.
That's a very important feature for data center use cases.
The PCIe hotplug driver goes to great lengths to avoid de-enumeration
and re-enumeration and instead allow for recovery from reset (see e.g.
the invocation of pci_dpc_recovered() and pciehp_ignore_dpc_link_change()
in pciehp_ist()).
So no, we do not want to remove devices in response to reset if we can
help it. We generally only de-enumerate and re-enumerate devices on
hotplug or if explicitly told to do so via sysfs "remove" / "rescan"
attributes.
Thanks,
Lukas
next prev parent reply other threads:[~2025-05-23 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 16:19 reset_slot() callback not respecting MPS config Niklas Cassel
2025-05-23 5:30 ` Wilfred Mallawa
2025-05-23 5:33 ` Lukas Wunner
2025-05-23 6:23 ` Wilfred Mallawa
2025-05-23 6:39 ` Manivannan Sadhasivam
2025-05-23 14:51 ` Lukas Wunner
2025-05-23 15:30 ` Manivannan Sadhasivam
2025-05-24 12:40 ` Lukas Wunner
2025-05-25 7:59 ` Manivannan Sadhasivam
2025-05-23 7:02 ` Niklas Cassel
2025-05-23 14:59 ` Lukas Wunner [this message]
2025-05-23 15:49 ` Manivannan Sadhasivam
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=aDCNPFBwHSPe9WLi@wunner.de \
--to=lukas@wunner.de \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=wilfred.mallawa@wdc.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