From: Lukas Wunner <lukas@wunner.de>
To: Shuai Xue <xueshuai@linux.alibaba.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-edac@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
helgaas@kernel.org, bhelgaas@google.com, 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
Subject: Re: [PATCH v6] PCI: hotplug: Add a generic RAS tracepoint for hotplug event
Date: Wed, 15 Jan 2025 10:33:39 +0100 [thread overview]
Message-ID: <Z4eA866i9eup6os3@wunner.de> (raw)
In-Reply-To: <7b482de1-fa19-45d6-bd05-f1c3ebb77192@linux.alibaba.com>
On Wed, Jan 15, 2025 at 11:59:13AM +0800, Shuai Xue wrote:
> 2025/1/15 10:41, Steven Rostedt:
> > On Wed, 15 Jan 2025 09:37:53 +0800 Shuai Xue <xueshuai@linux.alibaba.com> wrote:
> > > + trace_pci_hp_event(pci_name(ctrl->pcie->port),
> > > + slot_name(ctrl),
> > > + PCI_HOTPLUG_LINK_DOWN);
> >
> > Hmm, can't you just pass in the ctrl pointer to the tracepoint?
> >
> > trace_pci_hp_event(ctrl, PCI_HOTPLUG_LINK_DOWN);
> >
> > Then the above would be:
> >
> > TP_PROTO(struct controller *ctrl, int event),
> >
> > TP_ARGS(ctrl, event),
> >
> > TP_STRUCT__entry(
> > __string( port_name, pci_name(ctrl->pcie->port) )
> > __string( slot, slot_name(ctrl) )
> > __field( int, event )
> >
> > and everything else could be the same.
>
> Maybe it's not a good idea.
>
> I think pci_hp_event is a generic event for pciehp, shpchp, octep_hp, etc.
> But each hotplug driver has different `struct controller` and slot_name().
[...]
> So, IMHO, pass port_name and slot_name from each driver is more simple.
>
> + @Lukas for hotplug part.
You're right Shuai, there's several hotplug drivers in drivers/pci/hotplug/
and pciehp is just one of them. It's quite possible that other drivers
besides pciehp will want to add trace points as well. For consistency,
the trace event definitions need to work for all drivers.
Thanks,
Lukas
next prev parent reply other threads:[~2025-01-15 9:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 1:37 [PATCH v6] PCI: hotplug: Add a generic RAS tracepoint for hotplug event Shuai Xue
2025-01-15 2:41 ` Steven Rostedt
2025-01-15 3:59 ` Shuai Xue
2025-01-15 9:33 ` Lukas Wunner [this message]
2025-01-15 15:05 ` Steven Rostedt
2025-01-18 5:13 ` kernel test robot
2025-01-18 17:52 ` kernel test robot
2025-02-24 3:38 ` Shuai Xue
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=Z4eA866i9eup6os3@wunner.de \
--to=lukas@wunner.de \
--cc=anil.s.keshavamurthy@intel.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=helgaas@kernel.org \
--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=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.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 \
--cc=xueshuai@linux.alibaba.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