mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vincent Donnefort <vdonnefort@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] ring-buffer: Add a MAINTAINERS category specific for the tracing ring-buffer
Date: Wed, 23 Sep 2026 09:06:37 +0100	[thread overview]
Message-ID: <arOIjWCRhnYxkUcR@google.com> (raw)
In-Reply-To: <20260908094035.0b180833@gandalf.local.home>

On Tue, Sep 08, 2026 at 09:40:35AM -0400, Steven Rostedt wrote:
> From: Steven Rostedt <rostedt@goodmis.org>
> 
> The ring buffer code in the tracing directory has always been decoupled
> from the tracing code. It had a clean abstracted API to allow it to be
> used by systems outside of tracing. The API even allowed the ring buffer
> code to be drastically changed without affecting the tracing sub-system.
> 
> Recently, Vincent Donnefort has been contributing a lot of work to enhance
> the ring buffer. He implemented the user space mappings and recently
> created a version to allow pKVM hypervisors to use the code to trace
> the hypervisor and expose the events to the user.
> 
> Create a separate category for maintaining the ring buffer code so that
> Vincent can become an official maintainer of it. His work has little to do
> with the tracing code itself. In the future, he may even be the main
> maintainer of the ring buffer.
> 
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> ---
>  MAINTAINERS | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 3a19da74d00c..71bd2f57055d 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -27778,6 +27778,22 @@ F:	kernel/trace/trace_irqsoff.c
>  F:	kernel/trace/trace_osnoise.c
>  F:	kernel/trace/trace_sched_wakeup.c
>  
> +TRACING RING BUFFER
> +M:	Steven Rostedt <rostedt@goodmis.org>
> +M:	Vincent Donnefort <vdonnefort@google.com>
> +M:	Masami Hiramatsu <mhiramat@kernel.org>
> +L:	linux-kernel@vger.kernel.org
> +L:	linux-trace-kernel@vger.kernel.org
> +S:	Maintained
> +Q:	https://patchwork.kernel.org/project/linux-trace-kernel/list/
> +T:	git git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
> +F:	Documentation/trace/ring-buffer*
> +F:	Documentation/trace/remotes.rst
> +F:	include/linux/ring-buffer*.h
> +F:	kernel/trace/*ring_buffer*.c

as it relates to simple_ring_buffer.c do you want to add here undefsyms_base.c?

> +F:	kernel/trace/remote*.c
> +F:	tools/testing/selftests/ring-buffer/
> +
>  TRADITIONAL CHINESE DOCUMENTATION
>  M:	Chen-Yu Yeh <chenyou910331@gmail.com>
>  M:	Weijie Yuan <wy@wyuan.org>
> -- 
> 2.53.0
> 

-- 
Vincent

  parent reply	other threads:[~2026-09-23  8:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 13:40 Steven Rostedt
2026-09-10 19:50 ` Steven Rostedt
2026-09-10 20:20   ` Vincent Donnefort
2026-09-21  9:30   ` Steven Rostedt
2026-09-23  8:06 ` Vincent Donnefort [this message]
2026-09-23  8:17   ` Steven Rostedt

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=arOIjWCRhnYxkUcR@google.com \
    --to=vdonnefort@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®