From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Purva Yeshi <purvayeshi550@gmail.com>,
rostedt@goodmis.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, corbet@lwn.net
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v4 2/2] docs: tracing: Refactor index.rst for clarity
Date: Tue, 18 Mar 2025 21:23:57 +0700 [thread overview]
Message-ID: <Z9mB_ZXp2bdXh0YN@archie.me> (raw)
In-Reply-To: <20250318113230.24950-2-purvayeshi550@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3050 bytes --]
On Tue, Mar 18, 2025 at 05:02:30PM +0530, Purva Yeshi wrote:
> diff --git a/Documentation/trace/index.rst b/Documentation/trace/index.rst
> index fecc4adf7..5ddd47ee7 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
> fprobetrace
> - tracepoints
> + fprobe
> + ring-buffer-design
> +
> +Event Tracing and Analysis
> +--------------------------
> +
> +A detailed explanation of event tracing mechanisms and their
> +applications.
> +
> +.. toctree::
> + :maxdepth: 1
> +
> events
> events-kmem
> events-power
> events-nmi
> events-msr
> - mmiotrace
> + boottime-trace
> histogram
> histogram-design
> - boottime-trace
> - debugging
> - hwlat_detector
> - osnoise-tracer
> - timerlat-tracer
> +
> +Hardware and Performance Tracing
> +--------------------------------
> +
> +This section covers tracing features that monitor hardware
> +interactions and system performance.
> +
> +.. toctree::
> + :maxdepth: 1
> +
> intel_th
> - ring-buffer-design
> - ring-buffer-map
> stm
> sys-t
> coresight/index
> - user_events
> rv/index
> hisi-ptt
> + mmiotrace
> + hwlat_detector
> + osnoise-tracer
> + timerlat-tracer
> +
> +User-Space Tracing
> +------------------
> +
> +These tools allow tracing user-space applications and
> +interactions.
> +
> +.. toctree::
> + :maxdepth: 1
> +
> + user_events
> +
> +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
LGTM, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-03-18 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 11:32 [PATCH v4 1/2] docs: tracing: Reduce maxdepth in index.rst for clarity Purva Yeshi
2025-03-18 11:32 ` [PATCH v4 2/2] docs: tracing: Refactor " Purva Yeshi
2025-03-18 14:23 ` Bagas Sanjaya [this message]
2025-03-21 14:25 ` Steven Rostedt
2025-04-08 0:55 ` Bagas Sanjaya
2025-03-18 14:22 ` [PATCH v4 1/2] docs: tracing: Reduce maxdepth in " 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=Z9mB_ZXp2bdXh0YN@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;
as well as URLs for NNTP newsgroup(s).