[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250723100559.7f0adb3c@batman.local.home>
Date: Wed, 23 Jul 2025 10:05:59 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Shuai Xue <xueshuai@...ux.alibaba.com>
Cc: lukas@...ner.de, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-edac@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, helgaas@...nel.org,
ilpo.jarvinen@...ux.intel.com, mattc@...estorage.com,
Jonathan.Cameron@...wei.com, bhelgaas@...gle.com, tony.luck@...el.com,
bp@...en8.de, mhiramat@...nel.org, mathieu.desnoyers@...icios.com,
oleg@...hat.com, naveen@...nel.org, davem@...emloft.net,
anil.s.keshavamurthy@...el.com, mark.rutland@....com, peterz@...radead.org,
tianruidong@...ux.alibaba.com
Subject: Re: [PATCH v9 2/2] PCI: trace: Add a RAS tracepoint to monitor link
speed changes
On Wed, 23 Jul 2025 11:31:08 +0800
Shuai Xue <xueshuai@...ux.alibaba.com> wrote:
> + TP_printk("%s type:%d, reason:%d, cur_bus_speed:%s, max_bus_speed:%s, width:%u, flit_mode:%u, status:%s\n",
> + __get_str(port_name),
> + __entry->type,
> + __entry->reason,
> + pci_speed_string(__entry->cur_bus_speed),
> + pci_speed_string(__entry->max_bus_speed),
Hmm, I guess pci_speed_string() should be added to libtraceveent so
that perf and trace-cmd parses it correctly. I guess rasdaemon would
want that too (which also uses libtraceevent).
-- Steve
> + __entry->width,
> + __entry->flit_mode,
> + __print_flags((unsigned long)__entry->link_status, "|",
> + LNKSTA_FLAGS)
> + )
> +);
Powered by blists - more mailing lists