mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gabriele Monaco <gmonaco@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
	"Gabriele Monaco" <gmonaco@redhat.com>,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
	"Nam Cao" <namcao@linutronix.de>
Subject: [GIT PULL] rv changes for v6.19 (for-next)
Date: Tue, 11 Nov 2025 13:24:15 +0100	[thread overview]
Message-ID: <20251111122416.96930-1-gmonaco@redhat.com> (raw)

Steve,

The following changes since commit e9a6fb0bcdd7609be6969112f3fbfcce3b1d4a7c:

  Linux 6.18-rc5 (2025-11-09 15:10:19 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gmonaco/linux.git rv-6.19-next

for you to fetch changes up to 69d8895cb9a9f6450374577af8584c2e21cb5a9f:

  rv: Add explicit lockdep context for reactors (2025-11-11 13:18:56 +0100)

----------------------------------------------------------------
Summary of changes:

* Adapt the ftracetest script to be run from a different folder, this
  uses the already existing OPT_TEST_DIR but extends it further to run
  independent tests, then add an --rv flag to allow using the script for
  testing RV (mostly) independently on ftrace.
* Add basic RV selftests in selftests/verification to validate things
  like available/enabled monitors and reactors. This could have caught
  the bug introducing kernel panic solved above. Tests use ftracetest.
* Convert react() function in reactor to use va_list directly and use a
  central helper to handle the variadic arguments. Clean up macros and
  mark functions as static.
* Add lockdep annotations to reactors to have lockdep complain if they
  are called from improper context. Useful to develop new reactors. This
  highlights a warning in the panic reactor that is related to the
  printk subsystem and not to RV.

----------------------------------------------------------------
Gabriele Monaco (2):
      selftest/ftrace: Generalise ftracetest to use with RV
      selftests/verification: Add initial RV tests

Thomas Weißschuh (3):
      rv: Pass va_list to reactors
      rv: Make rv_reacting_on() static
      rv: Add explicit lockdep context for reactors

 MAINTAINERS                                        |  1 +
 include/linux/rv.h                                 | 11 ++--
 include/rv/da_monitor.h                            | 35 +++-------
 include/rv/ltl_monitor.h                           | 18 ++----
 kernel/trace/rv/reactor_panic.c                    |  6 +-
 kernel/trace/rv/reactor_printk.c                   |  6 +-
 kernel/trace/rv/rv_reactors.c                      | 22 ++++++-
 tools/testing/selftests/ftrace/ftracetest          | 34 +++++++---
 .../ftrace/test.d/00basic/mount_options.tc         |  2 +-
 tools/testing/selftests/ftrace/test.d/functions    |  6 +-
 tools/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 ++++++++++++++++++++
 .../verification/test.d/rv_monitors_available.tc   | 18 ++++++
 .../verification/test.d/rv_wwnr_printk.tc          | 30 +++++++++
 .../selftests/verification/verificationtest-ktap   |  8 +++
 20 files changed, 322 insertions(+), 69 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 100755 tools/testing/selftests/verification/verificationtest-ktap

Cc: Gabriele Monaco <gmonaco@redhat.com>
Cc: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
Cc: Nam Cao <namcao@linutronix.de>


                 reply	other threads:[~2025-11-11 12:25 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=20251111122416.96930-1-gmonaco@redhat.com \
    --to=gmonaco@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namcao@linutronix.de \
    --cc=rostedt@goodmis.org \
    --cc=thomas.weissschuh@linutronix.de \
    /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

all inboxes | Powered by JetHome®