linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shuai Xue <xueshuai@linux.alibaba.com>
To: Steven Rostedt <rostedt@goodmis.org>, Lukas Wunner <lukas@wunner.de>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-edac@vger.kernel.org, linux-trace-kernel@vger.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
Subject: Re: [PATCH v3] PCI: hotplug: Add a generic RAS tracepoint for hotplug event
Date: Fri, 22 Nov 2024 09:53:10 +0800	[thread overview]
Message-ID: <3f9b87c0-ff22-433f-adca-80716502c28f@linux.alibaba.com> (raw)
In-Reply-To: <20241121084354.4a554829@gandalf.local.home>



在 2024/11/21 21:43, Steven Rostedt 写道:
> On Thu, 21 Nov 2024 19:34:31 +0800
> Shuai Xue <xueshuai@linux.alibaba.com> wrote:
> 
>> Sure, I can reorganize the directory. You have two optional proposals:
>>
>> 1. /sys/kernel/debug/tracing/events/pci_hp_event
> 
> I'm guessing the above has TRACING_SYSTEM = pci_hp_event ? That is, the
> above is a system and not an event.
> 
>> 2. /sys/kernel/debug/tracing/events/pci/pci_hp_event
> 
> Whereas here, it's an event.
> 
>>
>> I personally prefer the second approach. However, I'll defer the final decision
>> to the tracing subsystem maintainer, considering their expertise and
>> familiarity with the existing conventions.
> 
> Normally the system is determined by the users of the tracing
> infrastructure and not the tracing maintainers. But I can give you some
> guidelines.
> 
> The "system" level:
> 
>    /sys/kernel/tracing/events/<system>
> 
> is just a way to group like events making it easier to enable them all at once:
> 
>   echo 1 > /sys/kernel/tracing/events/<system>/enable
> 
> or
> 
>    trace-cmd start -e <system>
> 
> The name of the "system" should be something that all the events underneath
> represent. Note, although events in two different systems can have the same
> name, it's best to try to keep them all unique. That's because if you have:
> 
> 
>   systemA/foo  and systemB/foo
> 
> If you add to the kernel command line: trace_event=foo
> it will enable both events. Although that could be fixed with: trace_event=systemA:foo
> 
> Note: trace_event=systemA  would enable all systemA events at boot.
> 
> That said, is all these events going to be related to hotplug? If so, you
> probably want "hotplug" or "hp" in the system name. If you make it just
> "pci", then it will be expected that all the events will be related to PCI
> in general.

I think Lukas is asking for a system for pci related tracepoint.

> 
> Does that help?

Yes, it really does.

> 
> -- Steve

Thanks a lot.

Best Regards,
Shuai


      parent reply	other threads:[~2024-11-22  1:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20 12:43 [PATCH v3] PCI: hotplug: Add a generic RAS tracepoint for hotplug event Shuai Xue
2024-11-21  9:27 ` Lukas Wunner
2024-11-21 11:34   ` Shuai Xue
2024-11-21 13:43     ` Steven Rostedt
2024-11-21 23:09       ` Lukas Wunner
2024-11-22  0:08         ` Steven Rostedt
2024-11-22  6:25           ` Shuai Xue
2024-11-22 10:29             ` Lukas Wunner
2024-11-22  1:53       ` 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=3f9b87c0-ff22-433f-adca-80716502c28f@linux.alibaba.com \
    --to=xueshuai@linux.alibaba.com \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=davem@davemloft.net \
    --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=mhiramat@kernel.org \
    --cc=naveen@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --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;
as well as URLs for NNTP newsgroup(s).