From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Kernel Tracing <linux-trace-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Jonathan Corbet <corbet@lwn.net>,
Purva Yeshi <purvayeshi550@gmail.com>
Subject: Re: [PATCH 2/2] Documentation: trace: Refactor toctree
Date: Wed, 16 Apr 2025 09:29:10 +0700 [thread overview]
Message-ID: <Z_8V9jY_GskZNrme@archie.me> (raw)
In-Reply-To: <20250415100617.08ab9e08@gandalf.local.home>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
On Tue, Apr 15, 2025 at 10:06:17AM -0400, Steven Rostedt wrote:
> > +Core Tracing Frameworks
> > +-----------------------
> > +
> > +The following are the primary tracing frameworks integrated into
> > +the Linux kernel.
> > +
> > +.. toctree::
> > + :maxdepth: 1
> > +
> > ftrace
> > + ftrace-design
> > ftrace-uses
> > - fprobe
> > kprobes
> > kprobetrace
> > uprobetracer
>
> I think the uprobetracer can go into the user space tracing below.
> As uprobes attaches to user space programs.
>
> > fprobetrace
> > - tracepoints
> > + fprobe
> > + ring-buffer-design
> > +
>
> [..]
>
> > +
> > +User-Space Tracing
> > +------------------
> > +
> > +These tools allow tracing user-space applications and
> > +interactions.
> > +
> > +.. toctree::
> > + :maxdepth: 1
> > +
> > + user_events
>
> uprobetracer
>
Will be addressed in v2.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-04-16 2:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 3:46 [PATCH 0/2] Table of contents refactoring for tracing docs Bagas Sanjaya
2025-04-15 3:46 ` [PATCH 1/2] Documentation: trace: Reduce toctree depth Bagas Sanjaya
2025-04-15 3:46 ` [PATCH 2/2] Documentation: trace: Refactor toctree Bagas Sanjaya
2025-04-15 14:06 ` Steven Rostedt
2025-04-16 2:29 ` Bagas Sanjaya [this message]
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=Z_8V9jY_GskZNrme@archie.me \
--to=bagasdotme@gmail.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=purvayeshi550@gmail.com \
--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
all inboxes | Powered by JetHome®