From: Steven Rostedt <rostedt@goodmis.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
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: Tue, 15 Apr 2025 10:06:17 -0400 [thread overview]
Message-ID: <20250415100617.08ab9e08@gandalf.local.home> (raw)
In-Reply-To: <20250415034613.21305-3-bagasdotme@gmail.com>
On Tue, 15 Apr 2025 10:46:13 +0700
Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>
> Hi Steven,
>
> I remove your Acked-by: since I massage the patch description. Would you mind
> to re-add yours?
Sure, I do have one comment below.
>
> Thanks.
>
> Documentation/trace/index.rst | 94 +++++++++++++++++++++++++++++------
> 1 file changed, 79 insertions(+), 15 deletions(-)
>
> diff --git a/Documentation/trace/index.rst b/Documentation/trace/index.rst
> index fecc4adf70a830..5ddd47ee781211 100644
> --- a/Documentation/trace/index.rst
> +++ b/Documentation/trace/index.rst
> @@ -1,39 +1,103 @@
> -==========================
> -Linux Tracing Technologies
> -==========================
> +================================
> +Linux Tracing Technologies Guide
> +================================
> +
> +Tracing in the Linux kernel is a powerful mechanism that allows
> +developers and system administrators to analyze and debug system
> +behavior. This guide provides documentation on various tracing
> +frameworks and tools available in the Linux kernel.
> +
> +Introduction to Tracing
> +-----------------------
> +
> +This section provides an overview of Linux tracing mechanisms
> +and debugging approaches.
>
> .. toctree::
> :maxdepth: 1
>
> - ftrace-design
> + debugging
> + tracepoints
> tracepoint-analysis
> + ring-buffer-map
> +
> +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
-- Steve
> +
> +Additional Resources
> +--------------------
> +
> +For more details, refer to the respective documentation of each
> +tracing tool and framework.
> +
> +.. only:: subproject and html
> +
> + Indices
> + =======
> +
> + * :ref:`genindex`
> \ No newline at end of file
next prev parent reply other threads:[~2025-04-15 14:04 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 [this message]
2025-04-16 2:29 ` Bagas Sanjaya
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=20250415100617.08ab9e08@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=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 \
/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®