All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shuai Xue <xueshuai@linux.alibaba.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: 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, 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 v9 2/2] PCI: trace: Add a RAS tracepoint to monitor link speed changes
Date: Fri, 25 Jul 2025 11:15:25 +0800	[thread overview]
Message-ID: <bcc697cb-bee6-4295-8488-8ad6b46491cf@linux.alibaba.com> (raw)
In-Reply-To: <20250724230647.1875702f@gandalf.local.home>



在 2025/7/25 11:06, Steven Rostedt 写道:
> On Fri, 25 Jul 2025 10:59:16 +0800
> Shuai Xue <xueshuai@linux.alibaba.com> wrote:
> 
>> Thank you so much for the detailed guidance and the excellent example!
>> This makes it much clearer how to implement the libtraceevent support.
>>
>> Should I include the libtraceevent plugin patch in the same kernel patch
>> series, or submit it separately? I'm not sure about the best practice
>> here.
> 
> No, libtraceevent lives outside the kernel tree.
> 
>>
>>>
>>> -- Steve
>>
>> I'll work on the libtraceevent patch and submit it according to your
>> guidance. Thanks again for the clear direction and the documentation
>> link!
> 
> Make a patch against: git://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git
> 
> Follow the same procedure as you would for submitting to the linux kernel,
> but instead of sending it to LKML, send it to: linux-trace-devel@vger.kernel.org
> 
> You don't even need to Cc me. I'll get it from that mailing list.
> 
> Patchwork is here: https://patchwork.kernel.org/project/linux-trace-devel/list/
> 
> -- Steve

Hi Steve,

Perfect, thank you for the clear instructions!

I'll work on the plugin and submit it to the trace-devel list once this
patch set is merged in upstream.

Thanks again for all the guidance!
Best regards,
Shuai


  reply	other threads:[~2025-07-25  3:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23  3:31 [PATCH v9 0/2] add PCI hotplug and PCIe link tracepoint Shuai Xue
2025-07-23  3:31 ` [PATCH v9 1/2] PCI: trace: Add a generic RAS tracepoint for hotplug event Shuai Xue
2025-07-25 21:09   ` Bjorn Helgaas
2025-07-28  9:05     ` Shuai Xue
2025-07-23  3:31 ` [PATCH v9 2/2] PCI: trace: Add a RAS tracepoint to monitor link speed changes Shuai Xue
2025-07-23 14:05   ` Steven Rostedt
2025-07-25  2:11     ` Shuai Xue
2025-07-25  2:25       ` Steven Rostedt
2025-07-25  2:59         ` Shuai Xue
2025-07-25  3:06           ` Steven Rostedt
2025-07-25  3:15             ` Shuai Xue [this message]
2025-07-23 19:30   ` kernel test robot
2025-07-24 14:06     ` Steven Rostedt
2025-07-25  2:31       ` Shuai Xue
2025-07-25  2:57         ` Steven Rostedt
2025-07-25  3:18           ` Shuai Xue
2025-07-25 21:09   ` Bjorn Helgaas
2025-07-26  7:51     ` Lukas Wunner
2025-07-28  9:28       ` Shuai Xue
2025-07-28  9:17     ` Shuai Xue
2025-09-18 23:06 ` [PATCH v9 0/2] add PCI hotplug and PCIe link tracepoint Bjorn Helgaas
2025-09-19  1:40   ` 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=bcc697cb-bee6-4295-8488-8ad6b46491cf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.