All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Daniel Bristot de Oliveira <bristot@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Clark Williams <williams@redhat.com>,
	Juri Lelli <juri.lelli@redhat.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-trace-devel@vger.kernel.org
Subject: [PATCH V2 00/11] rtla: Improved tracing support
Date: Mon, 21 Feb 2022 23:16:45 +0100	[thread overview]
Message-ID: <cover.1645481500.git.bristot@kernel.org> (raw)

This set introduces some tracing facilities to rtla tools:

- Add the possibility to change the tracing_thresh to osnoise,
allowing a fine tune of OS noise detection.

- Add the auto-tracing feature (-a threshold us), which aims
helping the first approach to a problem by setting common
tracing features with a single parameter.

- Add -e/--event option, allowing osnoise and timerlat to
enable additional trace events via (possible multiple)
-e sys:event options.

- Add the --filter option to filter the previous -e event.

- Add the --trigger option to allow the usage of tracing
trigger of the previously set -e event. If the trigger
is hist: one, rtla automatically saves the hist file
associated with the -e event.

Depends on "rtla: Some RTLA fixes for 5.17":
   https://lore.kernel.org/lkml/cover.1645206561.git.bristot@kernel.org/

Changes from V1:
 - Add -e to osnoise/timerlat hist
 - Add --trigger
 - Add --filter
 - Add support to save hist file
 - Function name refactoring

Daniel Bristot de Oliveira (11):
  rtla/osnoise: Add support to adjust the tracing_thresh
  rtla/osnoise: Add an option to set the threshold
  rtla/osnoise: Add the automatic trace option
  rtla/timerlat: Add the automatic trace option
  rtla/trace: Add trace events helpers
  rtla: Add -e/--event support
  rtla/trace: Add trace event trigger helpers
  rtla: Add --trigger support
  rtla/trace: Add trace event filter helpers
  rtla: Add --filter support
  rtla/trace: Save event histogram output to a file

 Documentation/tools/rtla/common_options.rst   |  19 +
 .../tools/rtla/common_osnoise_options.rst     |  10 +
 .../tools/rtla/common_timerlat_options.rst    |   7 +
 tools/tracing/rtla/src/osnoise.c              |  83 +++++
 tools/tracing/rtla/src/osnoise.h              |   8 +
 tools/tracing/rtla/src/osnoise_hist.c         |  87 ++++-
 tools/tracing/rtla/src/osnoise_top.c          |  83 ++++-
 tools/tracing/rtla/src/timerlat_hist.c        |  78 ++++-
 tools/tracing/rtla/src/timerlat_top.c         |  73 +++-
 tools/tracing/rtla/src/trace.c                | 326 ++++++++++++++++++
 tools/tracing/rtla/src/trace.h                |  22 ++
 11 files changed, 782 insertions(+), 14 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-02-21 22:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 22:16 Daniel Bristot de Oliveira [this message]
2022-02-21 22:16 ` [PATCH V2 01/11] rtla/osnoise: Add support to adjust the tracing_thresh Daniel Bristot de Oliveira
2022-02-21 22:16 ` [PATCH V2 02/11] rtla/osnoise: Add an option to set the threshold Daniel Bristot de Oliveira
2022-02-21 22:16 ` [PATCH V2 03/11] rtla/osnoise: Add the automatic trace option Daniel Bristot de Oliveira
2022-02-21 22:16 ` [PATCH V2 04/11] rtla/timerlat: " Daniel Bristot de Oliveira
2022-02-21 22:16 ` [PATCH V2 05/11] rtla/trace: Add trace events helpers Daniel Bristot de Oliveira
2022-02-21 22:16 ` [PATCH V2 06/11] rtla: Add -e/--event support Daniel Bristot de Oliveira
2022-02-21 22:16 ` [PATCH V2 07/11] rtla/trace: Add trace event trigger helpers Daniel Bristot de Oliveira
2022-02-21 22:16 ` [PATCH V2 08/11] rtla: Add --trigger support Daniel Bristot de Oliveira
2022-02-21 22:16 ` [PATCH V2 09/11] rtla/trace: Add trace event filter helpers Daniel Bristot de Oliveira
2022-02-21 22:16 ` [PATCH V2 10/11] rtla: Add --filter support Daniel Bristot de Oliveira
2022-02-21 22:16 ` [PATCH V2 11/11] rtla/trace: Save event histogram output to a file 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.1645481500.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=linux-trace-devel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.