From: Tomas Glozar <tglozar@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-trace-kernel <linux-trace-kernel@vger.kernel.org>,
Tomas Glozar <tglozar@redhat.com>
Subject: [GIT PULL] RTLA changes for 7.3
Date: Wed, 5 Aug 2026 17:10:55 +0200 [thread overview]
Message-ID: <20260805151055.870722-1-tglozar@redhat.com> (raw)
Steven,
The following changes since commit 075b74841bd0065a3bda3440873c747938e69b68:
Linux 7.2-rc6 (2026-08-02 16:24:24 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tglozar/linux.git tags/rtla-v7.3
for you to fetch changes up to 0ad45018ace734e3a21c8b15280df65b429135d1:
rtla/cli: Unify and improve handling of invalid option arguments (2026-08-05 10:14:40 +0200)
----------------------------------------------------------------
RTLA patches for 7.3
- Extend support for unsetting CLI options
libsubcmd auto-generates "--no-<option>" to unset options, provided
the option callback supports it. Implement this for RTLA CLI beyond
boolean options, and document the few exceptions that are left out.
- Test all tracer options in runtime tests
Verify that RTLA sets osnoise/timerlat options correctly by reading them
from tracefs during runtime tests.
- Improve range validation for option arguments
Make CLI range validation consistent with the kernel limits and unify
implementation and error messages between options.
- Improve invalid option argument parsing
Consistently reject invalid values for numeric option arguments with
a unified error message for all options.
Signed-off-by: Tomas Glozar <tglozar@redhat.com>
----------------------------------------------------------------
Tomas Glozar (7):
rtla: Allow unsetting non-list custom-callback CLI options
rtla: Add unit tests for unset in opt callbacks
rtla: Add unit tests for CLI with unset
Documentation/rtla: Document unsetting options
rtla/tests: Test all tracer options in runtime tests
rtla/cli: Unify and improve range validation logic
rtla/cli: Unify and improve handling of invalid option arguments
Documentation/tools/rtla/common_appendix.txt | 17 +
Documentation/tools/rtla/common_options.txt | 13 +-
.../tools/rtla/common_osnoise_options.txt | 4 +
.../tools/rtla/common_timerlat_options.txt | 4 +
tools/tracing/rtla/src/cli.c | 42 +-
tools/tracing/rtla/src/cli_p.h | 497 ++++++++++++-------
tools/tracing/rtla/tests/engine.sh | 41 +-
tools/tracing/rtla/tests/hwnoise.t | 3 +
tools/tracing/rtla/tests/osnoise.t | 39 +-
.../rtla/tests/scripts/check-osnoise-option.sh | 16 +
.../rtla/tests/scripts/check-tracefs-value.sh | 11 +
tools/tracing/rtla/tests/timerlat.t | 40 +-
tools/tracing/rtla/tests/unit/cli_opt_callback.c | 534 ++++++++++++++-------
tools/tracing/rtla/tests/unit/osnoise_hist_cli.c | 18 +
tools/tracing/rtla/tests/unit/osnoise_top_cli.c | 18 +
tools/tracing/rtla/tests/unit/timerlat_hist_cli.c | 18 +
tools/tracing/rtla/tests/unit/timerlat_top_cli.c | 18 +
17 files changed, 949 insertions(+), 384 deletions(-)
create mode 100755 tools/tracing/rtla/tests/scripts/check-osnoise-option.sh
create mode 100755 tools/tracing/rtla/tests/scripts/check-tracefs-value.sh
reply other threads:[~2026-08-05 15:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260805151055.870722-1-tglozar@redhat.com \
--to=tglozar@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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