From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: Daniel Bristot de Oliveira <bristot@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Juri Lelli <juri.lelli@redhat.com>,
Clark Williams <williams@redhat.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH V2 0/6] Add osnoise/options file
Date: Wed, 23 Nov 2022 18:06:18 +0100 [thread overview]
Message-ID: <cover.1669115208.git.bristot@kernel.org> (raw)
Was: Allow osnoise tracer to run without workload [1]
After adding the osnoise/options file, a set of on/off options
came to my mind, most based on discussions while debugging problems
with Juri and Clark.
So, this series now goes beyond running osnoise without a workload
by adding a set of practical options using the new osnoise/options file.
The [NO_]OSNOISE_WORKLOAD option allows the tracer to be dispatched
without workload, making the osnoise: tracepoints to become
generic events to measure the execution time of *any* task on Linux.
The PANIC_ON_STOP option facilitates the vmcore generation to aid
in the latency analysis using a crash dump.
The OSNOISE_PREEMPT_DISABLE and OSNOISE_IRQ_DISABLE options refine
the type of noise that the osnoise tracer detects, allowing the
tool to measure only IRQ-related noise, or NMI/HW-related noise,
respectively.
Each patch has a description of the options and the last patch
documents them in the osnoise documentation file.
[1] https://lore.kernel.org/r/cover.1668692096.git.bristot@kernel.org/
Changes from v1:
- Changed the cover letter topic
- Add Acked-by Masami to the first patch
- Add the PANIC_ON_STOP option
- Add the OSNOISE_PREEMPT_DISABLE and OSNOISE_IRQ_DISABLE options
- Improved the documentationa
Daniel Bristot de Oliveira (6):
tracing/osnoise: Fix duration type
tracing/osnoise: Add osnoise/options file
tracing/osnoise: Add OSNOISE_WORKLOAD option
tracing/osnoise: Add PANIC_ON_STOP option
tracing/osnoise: Add preempt and/or irq disabled options
Documentation/osnoise: Add osnoise/options documentation
Documentation/trace/osnoise-tracer.rst | 32 +++-
kernel/trace/trace_osnoise.c | 242 +++++++++++++++++++++++--
2 files changed, 261 insertions(+), 13 deletions(-)
--
2.32.0
next reply other threads:[~2022-11-23 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 17:06 Daniel Bristot de Oliveira [this message]
2022-11-23 17:06 ` [PATCH V2 1/6] tracing/osnoise: Fix duration type Daniel Bristot de Oliveira
2022-11-23 17:06 ` [PATCH V2 2/6] tracing/osnoise: Add osnoise/options file Daniel Bristot de Oliveira
2022-11-23 17:06 ` [PATCH V2 3/6] tracing/osnoise: Add OSNOISE_WORKLOAD option Daniel Bristot de Oliveira
2022-11-23 17:06 ` [PATCH V2 4/6] tracing/osnoise: Add PANIC_ON_STOP option Daniel Bristot de Oliveira
2022-11-23 17:06 ` [PATCH V2 5/6] tracing/osnoise: Add preempt and/or irq disabled options Daniel Bristot de Oliveira
2022-11-23 17:06 ` [PATCH V2 6/6] Documentation/osnoise: Add osnoise/options documentation 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=cover.1669115208.git.bristot@kernel.org \
--to=bristot@kernel.org \
--cc=corbet@lwn.net \
--cc=juri.lelli@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=williams@redhat.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;
as well as URLs for NNTP newsgroup(s).