From: Shuai Xue <xueshuai@linux.alibaba.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: tony.luck@intel.com, bp@alien8.de, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, oleg@redhat.com,
naveen@kernel.org, davem@davemloft.net,
anil.s.keshavamurthy@intel.com, mark.rutland@arm.com,
peterz@infradead.org, tianruidong@linux.alibaba.com,
rostedt@goodmis.org, lukas@wunner.de, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, helgaas@kernel.org,
ilpo.jarvinen@linux.intel.com, mattc@purestorage.com,
Jonathan.Cameron@huawei.com
Subject: Re: [PATCH v13 0/3] PCI: trace: Add a RAS tracepoint to monitor link speed changes
Date: Tue, 9 Dec 2025 21:19:00 +0800 [thread overview]
Message-ID: <bed37798-8c38-4669-b841-45924473696a@linux.alibaba.com> (raw)
In-Reply-To: <1f9ee237-9d62-4c33-83c3-ce4d9ca9497f@linux.alibaba.com>
在 2025/11/4 17:34, Shuai Xue 写道:
>
>
> 在 2025/10/25 19:41, Shuai Xue 写道:
>> changes since v12:
>> - add Reviewed-by tag for PATCH 1 from Steve
>> - add Reviewed-by tag for PATCH 1-3 from Ilpo
>> - add comments for why use string to define tracepoint per Steve
>> - minor doc improvements from Ilpo
>> - remove use pci_speed_string to fix PCI dependends which cause build error on sparc64
>>
>> changes since v11:
>> - rebase to Linux 6.18-rc1 (no functional changes)
>>
>> changes since v10:
>> - explicitly include header file per Ilpo
>> - add comma on any non-terminator entry per Ilpo
>> - compile trace.o under CONFIG_TRACING per Ilpo
>>
>> changes since v9:
>> - add a documentation about PCI tracepoints per Bjorn
>> - create a dedicated drivers/pci/trace.c that always defines the PCI tracepoints per Steve
>> - move tracepoint callite into __pcie_update_link_speed() per Lukas and Bjorn
>>
>> changes since v8:
>> - rewrite commit log from Bjorn
>> - move pci_hp_event to a common place (include/trace/events/pci.h) per Ilpo
>> - rename hotplug event strings per Bjorn and Lukas
>> - add PCIe link tracepoint per Bjorn, Lukas, and Ilpo
>>
>> changes since v7:
>> - replace the TRACE_INCLUDE_PATH to avoid macro conflict per Steven
>> - pick up Reviewed-by from Lukas Wunner
>>
>> Hotplug events are critical indicators for analyzing hardware health, and
>> surprise link downs can significantly impact system performance and reliability.
>> In addition, PCIe link speed degradation directly impacts system performance and
>> often indicates hardware issues such as faulty devices, physical layer problems,
>> or configuration errors.
>>
>> This patch set add PCI hotplug and PCIe link tracepoint to help analyze PCI
>> hotplug events and PCIe link speed degradation.
>>
>> Shuai Xue (3):
>> PCI: trace: Add a generic RAS tracepoint for hotplug event
>> PCI: trace: Add a RAS tracepoint to monitor link speed changes
>> Documentation: tracing: Add documentation about PCI tracepoints
>>
>
> Hi, Bjorn,
>
> Gentle ping.
>
> Do you have any further concerns about this patch set?
>
> Shuai
Hi, all,
Gentle ping.
Thanks.
Shuai
prev parent reply other threads:[~2025-12-09 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 11:41 [PATCH v13 0/3] PCI: trace: Add a RAS tracepoint to monitor link speed changes Shuai Xue
2025-10-25 11:41 ` [PATCH v13 1/3] PCI: trace: Add a generic RAS tracepoint for hotplug event Shuai Xue
2025-10-25 11:41 ` [PATCH v13 2/3] PCI: trace: Add a RAS tracepoint to monitor link speed changes Shuai Xue
2025-10-25 11:41 ` [PATCH v13 3/3] Documentation: tracing: Add documentation about PCI tracepoints Shuai Xue
2025-12-09 13:59 ` [External] : " ALOK TIWARI
2025-12-10 1:56 ` Shuai Xue
2025-11-04 9:34 ` [PATCH v13 0/3] PCI: trace: Add a RAS tracepoint to monitor link speed changes Shuai Xue
2025-12-09 13:19 ` Shuai Xue [this message]
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=bed37798-8c38-4669-b841-45924473696a@linux.alibaba.com \
--to=xueshuai@linux.alibaba.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mattc@purestorage.com \
--cc=mhiramat@kernel.org \
--cc=naveen@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tianruidong@linux.alibaba.com \
--cc=tony.luck@intel.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