From: Steven Rostedt <rostedt@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: "Gabriele Monaco" <gmonaco@redhat.com>,
"Nam Cao" <namcao@linutronix.de>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Subject: [for-next][PATCH 0/5] rv: Updates for v6.19
Date: Wed, 12 Nov 2025 17:19:46 -0500 [thread overview]
Message-ID: <20251112221946.389142361@kernel.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2534 bytes --]
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
latency/for-next
Head SHA1: 69d8895cb9a9f6450374577af8584c2e21cb5a9f
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
next reply other threads:[~2025-11-12 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 22:19 Steven Rostedt [this message]
2025-11-12 22:19 ` [for-next][PATCH 1/5] selftest/ftrace: Generalise ftracetest to use with RV Steven Rostedt
2025-11-12 22:19 ` [for-next][PATCH 2/5] selftests/verification: Add initial RV tests Steven Rostedt
2025-11-12 22:19 ` [for-next][PATCH 3/5] rv: Pass va_list to reactors Steven Rostedt
2025-11-12 22:19 ` [for-next][PATCH 4/5] rv: Make rv_reacting_on() static Steven Rostedt
2025-11-12 22:19 ` [for-next][PATCH 5/5] rv: Add explicit lockdep context for reactors Steven Rostedt
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=20251112221946.389142361@kernel.org \
--to=rostedt@kernel.org \
--cc=gmonaco@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namcao@linutronix.de \
--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