[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250718034616.26250-1-mattc@purestorage.com>
Date: Thu, 17 Jul 2025 21:46:16 -0600
From: Matthew W Carlis <mattc@...estorage.com>
To: helgaas@...nel.org
Cc: anil.s.keshavamurthy@...el.com,
bhelgaas@...gle.com,
bp@...en8.de,
davem@...emloft.net,
ilpo.jarvinen@...ux.intel.com,
linux-edac@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-pci@...r.kernel.org,
linux-trace-kernel@...r.kernel.org,
lukas@...ner.de,
mark.rutland@....com,
mathieu.desnoyers@...icios.com,
mattc@...estorage.com,
mhiramat@...nel.org,
naveen@...nel.org,
oleg@...hat.com,
peterz@...radead.org,
rostedt@...dmis.org,
tianruidong@...ux.alibaba.com,
tony.luck@...el.com,
xueshuai@...ux.alibaba.com
Subject: Re: [PATCH v8] PCI: hotplug: Add a generic RAS tracepoint for hotplug event
On Thu, Jul 17, 2025 Bjorn Helgaas wrote
> So I think your idea of adding current link speed/width to the "Link
> Up" event is still on the table, and that does sound useful to me.
We're already reading the link status register here to check DLLA so
it would be nice. I guess if everything is healthy we're probably already
at the maximum speed by this point.
> In the future we might add another tracepoint when we enumerate the
> device and know the Vendor/Device ID.
I think we might have someone who would be interested in doing it.
Powered by blists - more mailing lists