From: Shuah Khan <skhan@linuxfoundation.org>
To: corbet@lwn.net
Cc: sshefali021@gmail.com, kstewart@linuxfoundation.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] docs: add workload-tracing document to admin-guide
Date: Tue, 31 Jan 2023 15:09:34 -0700 [thread overview]
Message-ID: <5487c6cd-0156-b79c-4f44-0b897c404049@linuxfoundation.org> (raw)
In-Reply-To: <20230131220722.38892-1-skhan@linuxfoundation.org>
On 1/31/23 15:07, Shuah Khan wrote:
> 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
>
Sorry forgot to tag it v3 - will send again with the correct version.
-- Shuah
next prev parent reply other threads:[~2023-01-31 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 22:07 [PATCH] docs: add workload-tracing document to admin-guide Shuah Khan
2023-01-31 22:09 ` Shuah Khan [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-27 16:54 Shuah Khan
2023-01-27 17:13 ` Jonathan Corbet
2023-01-27 19:18 ` Shuah Khan
2023-01-27 23:49 ` 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=5487c6cd-0156-b79c-4f44-0b897c404049@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=kstewart@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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