From: Beau Belgrave <beaub@linux.microsoft.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: rostedt@goodmis.org, mhiramat@kernel.org, corbet@lwn.net,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: Document user_events ioctl code
Date: Wed, 3 Jul 2024 16:13:43 -0700 [thread overview]
Message-ID: <20240703231343.GA408-beaub@linux.microsoft.com> (raw)
In-Reply-To: <ZoXXe8Tl9pRD6-dd@localhost.localdomain>
On Wed, Jul 03, 2024 at 06:58:03PM -0400, Mathieu Desnoyers wrote:
> On 03-Jul-2024 10:25:01 PM, Beau Belgrave wrote:
> > The user events trace subsystem uses the 0x2A/'*' code for ioctls. These
> > are published via the uapi/linux/user_events.h header file.
> >
> > Add a line indicating user events as the owner of the 0x2A/'*' code and the
> > current sequence numbers that are in use (00-02).
> >
> > Signed-off-by: Beau Belgrave <beaub@linux.microsoft.com>
> > ---
> > Documentation/userspace-api/ioctl/ioctl-number.rst | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/Documentation/userspace-api/ioctl/ioctl-number.rst b/Documentation/userspace-api/ioctl/ioctl-number.rst
> > index a141e8e65c5d..191609fe4593 100644
> > --- a/Documentation/userspace-api/ioctl/ioctl-number.rst
> > +++ b/Documentation/userspace-api/ioctl/ioctl-number.rst
> > @@ -97,6 +97,8 @@ Code Seq# Include File Comments
> > '%' 00-0F include/uapi/linux/stm.h System Trace Module subsystem
> > <mailto:alexander.shishkin@linux.intel.com>
> > '&' 00-07 drivers/firewire/nosy-user.h
> > +'*' 00-02 uapi/linux/user_events.h User Events Subsystem
>
> You may want to consider reserving a wider sequence number range to plan
> ahead for future extensions to user events. This way you won't end up
> having to jump over sequence numbers eventually reserved by others
> within the '*' code.
>
> Thanks,
>
> Mathieu
Yeah, I thought about that, but really didn't know how greedy we could
be. At first I had all, but then thought we would never use all of that
sequence. We'll likely want a few more for libside integration.
Maybe I'll grab the first 16, that should leave a lot for others and
give us quite bit of growing room.
How many do you think we'll need for libside? I think we'd only need 2-3
personally.
Thanks,
-Beau
>
>
> > + <mailto:linux-trace-kernel@vger.kernel.org>
> > '1' 00-1F linux/timepps.h PPS kit from Ulrich Windl
> > <ftp://ftp.de.kernel.org/pub/linux/daemons/ntp/PPS/>
> > '2' 01-04 linux/i2o.h
> > --
> > 2.34.1
> >
>
> --
> Mathieu Desnoyers
> EfficiOS Inc.
> http://www.efficios.com
next prev parent reply other threads:[~2024-07-03 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 22:25 [PATCH] Documentation: Document user_events ioctl code Beau Belgrave
2024-07-03 22:58 ` Mathieu Desnoyers
2024-07-03 23:13 ` Beau Belgrave [this message]
2024-07-08 22:44 ` Masami Hiramatsu
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=20240703231343.GA408-beaub@linux.microsoft.com \
--to=beaub@linux.microsoft.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--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 \
/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;
as well as URLs for NNTP newsgroup(s).