From: Beau Belgrave <beaub@linux.microsoft.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
"Dmitry V. Levin" <ldv@strace.io>,
Vincent Donnefort <vdonnefort@google.com>,
mhiramat@kernel.org, kernel-team@android.com,
rdunlap@infradead.org, rppt@kernel.org, david@redhat.com,
linux-trace-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v23 3/5] tracing: Allow user-space mapping of the ring-buffer
Date: Wed, 3 Jul 2024 22:26:46 +0000 [thread overview]
Message-ID: <20240703222646.GA2025-beaub@linux.microsoft.com> (raw)
In-Reply-To: <20240702125126.50a6267c@rorschach.local.home>
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@efficios.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/
next prev parent reply other threads:[~2024-07-03 22:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 14:04 [PATCH v23 0/5] Introducing trace buffer mapping by user-space Vincent Donnefort
2024-05-10 14:04 ` [PATCH v23 1/5] ring-buffer: Allocate sub-buffers with __GFP_COMP Vincent Donnefort
2024-05-10 14:04 ` [PATCH v23 2/5] ring-buffer: Introducing ring-buffer mapping functions Vincent Donnefort
2024-05-10 14:06 ` David Hildenbrand
2024-05-10 14:04 ` [PATCH v23 3/5] tracing: Allow user-space mapping of the ring-buffer Vincent Donnefort
2024-06-30 10:53 ` Dmitry V. Levin
2024-06-30 12:40 ` Steven Rostedt
2024-07-02 14:36 ` Mathieu Desnoyers
2024-07-02 15:18 ` Steven Rostedt
2024-07-02 15:32 ` Mathieu Desnoyers
2024-07-02 16:44 ` Dmitry V. Levin
2024-07-02 16:51 ` Steven Rostedt
2024-07-02 17:37 ` Mathieu Desnoyers
2024-07-03 22:26 ` Beau Belgrave [this message]
2024-07-02 17:33 ` Dmitry V. Levin
2024-05-10 14:04 ` [PATCH v23 4/5] Documentation: tracing: Add ring-buffer mapping Vincent Donnefort
2024-05-10 14:04 ` [PATCH v23 5/5] ring-buffer/selftest: Add ring-buffer mapping test Vincent Donnefort
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=20240703222646.GA2025-beaub@linux.microsoft.com \
--to=beaub@linux.microsoft.com \
--cc=david@redhat.com \
--cc=kernel-team@android.com \
--cc=ldv@strace.io \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vdonnefort@google.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.