public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gabriele Monaco <gmonaco@redhat.com>
To: linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Nam Cao	 <namcao@linutronix.de>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	John Kacur <jkacur@redhat.com>,  Waylon Cude <wcude@redhat.com>,
	linux-trace-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 0/2] selftests/verification: Add initial RV tests
Date: Mon, 13 Oct 2025 13:51:56 +0200	[thread overview]
Message-ID: <03365f64c7f94daa39bcc7df45cac2928af2a570.camel@redhat.com> (raw)
In-Reply-To: <20250926094613.34030-1-gmonaco@redhat.com>

On Fri, 2025-09-26 at 11:46 +0200, Gabriele Monaco wrote:
> Add a series of tests to validate the RV tracefs API and basic
> functionality.
> 
> * available monitors:
>     Check that all monitors (from the monitors folder) appear as
>     available and have a description. Works with nested monitors.
> 
> * enable/disable:
>     Enable and disable all monitors and validate both the enabled file
>     and the enabled_monitors. Check that enabling container monitors
>     enables all nested monitors.
> 
> * reactors:
>     Set all reactors and validate the setting, also for nested monitors.
> 
> * wwnr with printk:
>     wwnr is broken on purpose, run it with a load and check that the
>     printk reactor works. Also validate disabling reacting_on or
>     monitoring_on prevents reactions.
> 
> These tests use the ftracetest suite. The first patch of the series
> adapts ftracetest to make this possible.
> 
> The enable/disable test cannot pass on upstream without the application
> of the fix in [1].

Steve, Nam, would you have time to have a look at this series.
If possible, I'd like to get this minimal selftest to next together with Nam's
(urgent) patches.

Thanks,
Gabriele

> 
> [1] - https://lore.kernel.org/lkml/87tt0t4u19.fsf@yellow.woof
> 
> To: Steven Rostedt <rostedt@goodmis.org>
> To: Nam Cao <namcao@linutronix.de>
> Cc: Masami Hiramatsu <mhiramat@kernel.org>
> Cc: John Kacur <jkacur@redhat.com>
> Cc: Waylon Cude <wcude@redhat.com>
> Cc: linux-trace-kernel@vger.kernel.org
> Cc: linux-kselftest@vger.kernel.org
> 
> Gabriele Monaco (2):
>   selftest/ftrace: Generalise ftracetest to use with RV
>   selftests/verification: Add initial RV tests
> 
>  MAINTAINERS                                   |  1 +
>  tools/testing/selftests/ftrace/ftracetest     | 34 ++++++---
>  .../ftrace/test.d/00basic/mount_options.tc    |  2 +-
>  .../testing/selftests/ftrace/test.d/functions |  6 +-
>  .../testing/selftests/verification/.gitignore |  2 +
>  tools/testing/selftests/verification/Makefile |  8 ++
>  tools/testing/selftests/verification/config   |  1 +
>  tools/testing/selftests/verification/settings |  1 +
>  .../selftests/verification/test.d/functions   | 39 ++++++++++
>  .../test.d/rv_monitor_enable_disable.tc       | 75 +++++++++++++++++++
>  .../verification/test.d/rv_monitor_reactor.tc | 68 +++++++++++++++++
>  .../test.d/rv_monitors_available.tc           | 18 +++++
>  .../verification/test.d/rv_wwnr_printk.tc     | 29 +++++++
>  .../verification/verificationtest-ktap        |  8 ++
>  14 files changed, 278 insertions(+), 14 deletions(-)
>  create mode 100644 tools/testing/selftests/verification/.gitignore
>  create mode 100644 tools/testing/selftests/verification/Makefile
>  create mode 100644 tools/testing/selftests/verification/config
>  create mode 100644 tools/testing/selftests/verification/settings
>  create mode 100644 tools/testing/selftests/verification/test.d/functions
>  create mode 100644
> tools/testing/selftests/verification/test.d/rv_monitor_enable_disable.tc
>  create mode 100644
> tools/testing/selftests/verification/test.d/rv_monitor_reactor.tc
>  create mode 100644
> tools/testing/selftests/verification/test.d/rv_monitors_available.tc
>  create mode 100644
> tools/testing/selftests/verification/test.d/rv_wwnr_printk.tc
>  create mode 100644 tools/testing/selftests/verification/verificationtest-ktap
> 
> 
> base-commit: cec1e6e5d1ab33403b809f79cd20d6aff124ccfe


  parent reply	other threads:[~2025-10-13 11:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-26  9:46 [PATCH 0/2] selftests/verification: Add initial RV tests Gabriele Monaco
2025-09-26  9:46 ` [PATCH 1/2] selftest/ftrace: Generalise ftracetest to use with RV Gabriele Monaco
2025-09-26  9:46 ` [PATCH 2/2] selftests/verification: Add initial RV tests Gabriele Monaco
2025-10-13 11:51 ` Gabriele Monaco [this message]
2025-10-13 11:56   ` [PATCH 0/2] " Nam Cao
2025-10-17  7:38 ` Nam Cao
2025-10-17  8:50   ` Gabriele Monaco

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=03365f64c7f94daa39bcc7df45cac2928af2a570.camel@redhat.com \
    --to=gmonaco@redhat.com \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=namcao@linutronix.de \
    --cc=rostedt@goodmis.org \
    --cc=wcude@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