[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240703222646.GA2025-beaub@linux.microsoft.com>
Date: Wed, 3 Jul 2024 22:26:46 +0000
From: Beau Belgrave <beaub@...ux.microsoft.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
"Dmitry V. Levin" <ldv@...ace.io>,
Vincent Donnefort <vdonnefort@...gle.com>, mhiramat@...nel.org,
kernel-team@...roid.com, rdunlap@...radead.org, rppt@...nel.org,
david@...hat.com, linux-trace-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-api@...r.kernel.org,
linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH v23 3/5] tracing: Allow user-space mapping of the
ring-buffer
On Tue, Jul 02, 2024 at 12:51:26PM -0400, Steven Rostedt wrote:
> On Tue, 2 Jul 2024 11:32:53 -0400
> Mathieu Desnoyers <mathieu.desnoyers@...icios.com> wrote:
>
> > If we use '*' for user events already, perhaps we'd want to consider
> > using the same range for the ring buffer ioctls ? Arguably one is
> > about instrumentation and the other is about ring buffer interaction
> > (data transport), but those are both related to tracing.
>
> Yeah, but I still rather keep them separate.
>
> Beau, care to send a patch adding an entry into that ioctl document for
> user events?
>
> -- Steve
Sure thing, sent one out [1].
Thanks,
-Beau
1. https://lore.kernel.org/linux-doc/20240703222501.1547-1-beaub@linux.microsoft.com/
Powered by blists - more mailing lists