From: Steven Rostedt <rostedt@goodmis.org>
To: Costa Shulyupin <costa.shul@redhat.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org,
Daniel Bristot de Oliveira <bristot@kernel.org>,
linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH] docs: move tracing tools
Date: Tue, 25 Apr 2023 13:48:24 -0400 [thread overview]
Message-ID: <20230425134824.5d57c431@gandalf.local.home> (raw)
In-Reply-To: <20230425130231.912349-1-costa.shul@redhat.com>
On Tue, 25 Apr 2023 16:02:30 +0300
Costa Shulyupin <costa.shul@redhat.com> wrote:
> from list of development tools to user tools
> because these tools work on running kernel
> and are invoked from user mode
Wait what? No!
The trace/ directory has a lot that is kernel internal only. Yes, it may
explain how user space can interact with it, but it's also how internal
kernel processes can use the ftrace infrastructure, and also explains a lot
of the kernel design of that code.
NACK!
-- Steve
>
> Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>
> ---
> Documentation/index.rst | 1 -
> Documentation/tools/index.rst | 1 +
> 2 files changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/index.rst b/Documentation/index.rst
> index 9dfdc826618c..81e1af951731 100644
> --- a/Documentation/index.rst
> +++ b/Documentation/index.rst
> @@ -56,7 +56,6 @@ Various other manuals with useful information for all kernel developers.
> dev-tools/index
> dev-tools/testing-overview
> kernel-hacking/index
> - trace/index
> fault-injection/index
> livepatch/index
> rust/index
> diff --git a/Documentation/tools/index.rst b/Documentation/tools/index.rst
> index 80488e290e10..6a9a44f7f88a 100644
> --- a/Documentation/tools/index.rst
> +++ b/Documentation/tools/index.rst
> @@ -12,6 +12,7 @@ more additions are needed here:
>
> rtla/index
> rv/index
> + ../trace/index
>
> .. only:: subproject and html
>
next prev parent reply other threads:[~2023-04-25 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 13:02 [PATCH] docs: move tracing tools Costa Shulyupin
2023-04-25 17:48 ` Steven Rostedt [this message]
2023-04-26 9:06 ` Daniel Bristot de Oliveira
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=20230425134824.5d57c431@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bristot@kernel.org \
--cc=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).