lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250724230647.1875702f@gandalf.local.home>
Date: Thu, 24 Jul 2025 23:06:47 -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 Fri, 25 Jul 2025 10:59:16 +0800
Shuai Xue <xueshuai@...ux.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@...r.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ