Re: [PATCH] tracing: Have memmapped ring buffer use ioctl of "R" range 0x20-2F

2024-07-02 Thread Google
On Tue, 2 Jul 2024 15:33:54 -0400 Steven Rostedt wrote: > From: "Steven Rostedt (Google)" > > To prevent conflicts with other ioctl numbers to allow strace to have an > idea of what is happening, add the rang of ioctls for the trace buffer > mapping from _IO("T", 0x1) to the range of "R" 0x20 -

Re: [PATCH] tracing: Have memmapped ring buffer use ioctl of "R" range 0x20-2F

2024-07-02 Thread Steven Rostedt
On Tue, 2 Jul 2024 15:38:10 -0400 Mathieu Desnoyers wrote: > On 2024-07-02 15:33, Steven Rostedt wrote: > > From: "Steven Rostedt (Google)" > > > > To prevent conflicts with other ioctl numbers to allow strace to have an > > idea of what is happening, add the rang of ioctls for the trace buffer

Re: [PATCH] tracing: Have memmapped ring buffer use ioctl of "R" range 0x20-2F

2024-07-02 Thread Mathieu Desnoyers
On 2024-07-02 15:33, Steven Rostedt wrote: From: "Steven Rostedt (Google)" To prevent conflicts with other ioctl numbers to allow strace to have an idea of what is happening, add the rang of ioctls for the trace buffer mapping from _IO("T", 0x1) to the range of "R" 0x20 - 0x2F. Link: https://

[PATCH] tracing: Have memmapped ring buffer use ioctl of "R" range 0x20-2F

2024-07-02 Thread Steven Rostedt
From: "Steven Rostedt (Google)" To prevent conflicts with other ioctl numbers to allow strace to have an idea of what is happening, add the rang of ioctls for the trace buffer mapping from _IO("T", 0x1) to the range of "R" 0x20 - 0x2F. Link: https://lore.kernel.org/linux-trace-kernel/2024063010