From: Chaosheng Qu <chaosheng.qu.linux@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Gabriele Monaco <gmonaco@redhat.com>
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] verification/rvgen: validate the monitor type
Date: Sat, 21 Nov 2026 19:31:27 +0800 [thread overview]
Message-ID: <cover.1795252297.git.chaosheng.qu.linux@gmail.com> (raw)
rvgen takes the monitor type on the command line and pastes it into the
generated monitor as RV_MON_<TYPE>. Nothing validates it, so a typo
produces a monitor that cannot build while the tool still exits 0.
Monitor.monitor_types already holds the accepted set; pass it to
argparse as choices. Patch 2 covers the rejection next to the other
error tests.
v2:
- Thread the series; 2/2 replies to this cover letter.
- Tag both patches verification/rvgen: and capitalise the subject.
- Patch content unchanged.
Link: https://lore.kernel.org/linux-trace-kernel/179447882046.254241.15114935256138596418@gmail.com/
Link: https://lore.kernel.org/linux-trace-kernel/179447882047.254241.3226415982233977960@gmail.com/
Testing: make check in tools/verification/rvgen -- 31/31 pass.
Chaosheng Qu (2):
verification/rvgen: Validate the monitor type
verification/rvgen: Cover an invalid monitor type
tools/verification/rvgen/__main__.py | 1 +
tools/verification/rvgen/tests/rvgen_monitor.t | 4 ++++
2 files changed, 5 insertions(+)
--
2.43.0
next reply other threads:[~2026-11-21 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-21 11:31 Chaosheng Qu [this message]
2026-11-21 11:31 ` [PATCH v2 1/2] verification/rvgen: Validate the monitor type Chaosheng Qu
2026-11-21 11:36 ` sashiko-bot
2026-11-21 11:31 ` [PATCH v2 2/2] verification/rvgen: Cover an invalid " Chaosheng Qu
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.1795252297.git.chaosheng.qu.linux@gmail.com \
--to=chaosheng.qu.linux@gmail.com \
--cc=gmonaco@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 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.