From: Jonathan Corbet <corbet@lwn.net>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
sshefali021@gmail.com, kstewart@linuxfoundation.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] docs: add workload-tracing document to admin-guide
Date: Thu, 02 Feb 2023 10:43:01 -0700 [thread overview]
Message-ID: <87edr8vu8q.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230131221105.39216-1-skhan@linuxfoundation.org>
Shuah Khan <skhan@linuxfoundation.org> writes:
> Add a new section to the admin-guide with information of interest to
> application developers and system integrators doing analysis of the
> Linux kernel for safety critical applications.
>
> This section will contain documents supporting analysis of kernel
> interactions with applications, and key kernel subsystems expectations.
>
> Add a new workload-tracing document to this new section.
>
> Signed-off-by: Shefali Sharma <sshefali021@gmail.com>
> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
> ---
> Changes since v2: Addressed review comments on v2
>
> Documentation/admin-guide/index.rst | 11 +
> .../admin-guide/workload-tracing.rst | 605 ++++++++++++++++++
> 2 files changed, 616 insertions(+)
> create mode 100644 Documentation/admin-guide/workload-tracing.rst
I've applied this with a couple of sphinx tweaks, including:
> diff --git a/Documentation/admin-guide/index.rst b/Documentation/admin-guide/index.rst
> index 5bfafcbb9562..f475554382e2 100644
> --- a/Documentation/admin-guide/index.rst
> +++ b/Documentation/admin-guide/index.rst
> @@ -56,6 +56,17 @@ ABI will be found here.
>
> sysfs-rules
>
> +This is the beginning of a section with information of interest to
> +application developers and system integrators doing analysis of the
> +Linux kernel for safety critical applications. Documents supporting
> +analysis of kernel interactions with applications, and key kernel
> +subsystems expectations will be found here.
> +
> +.. toctree::
> + :maxdepth: 1
> +
> + workload-tracing
> +
> The rest of this manual consists of various unordered guides on how to
> configure specific aspects of kernel behavior to your liking.
>
> diff --git a/Documentation/admin-guide/workload-tracing.rst b/Documentation/admin-guide/workload-tracing.rst
> new file mode 100644
> index 000000000000..5fad64b4ebd6
> --- /dev/null
> +++ b/Documentation/admin-guide/workload-tracing.rst
> @@ -0,0 +1,605 @@
> +.. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
> +
> +Discovering Linux kernel subsystems used by a workload
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++
This doesn't follow our normal conventions, so I made it:
> ======================================================
> Discovering Linux kernel subsystems used by a workload
> ======================================================
Instead.
Thanks,
jon
next prev parent reply other threads:[~2023-02-02 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 22:11 [PATCH v3] docs: add workload-tracing document to admin-guide Shuah Khan
2023-02-01 4:03 ` Bagas Sanjaya
2023-02-01 23:41 ` Jonathan Corbet
2023-02-02 7:45 ` Bagas Sanjaya
2023-02-02 17:43 ` Jonathan Corbet [this message]
2023-02-02 19:12 ` Shuah Khan
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=87edr8vu8q.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=kstewart@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=sshefali021@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