All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Gabriele Monaco <gmonaco@redhat.com>
Cc: linux-kernel@vger.kernel.org, Nam Cao <namcao@linutronix.de>,
	Tomas Glozar <tglozar@redhat.com>, Juri Lelli <jlelli@redhat.com>,
	Clark Williams <williams@redhat.com>,
	John Kacur <jkacur@redhat.com>
Subject: Re: [PATCH 0/5] tools/verification: Improvements to rv and rvgen
Date: Thu, 24 Jul 2025 10:40:11 -0400	[thread overview]
Message-ID: <20250724104011.7b4e11d9@batman.local.home> (raw)
In-Reply-To: <20250723161240.194860-1-gmonaco@redhat.com>

On Wed, 23 Jul 2025 18:12:35 +0200
Gabriele Monaco <gmonaco@redhat.com> wrote:

> This series introduces various improvements to the rv/rvgen tools as
> first posted in [1]. It also adapts generated kernel files accordingly.
> 
> Specifically:
> 
> Patch 1 fixes the behaviour of the rv tool with -s and idle tasks.
> 
> Patch 2 allows the rv tool to gracefully terminate with SIGTERM
> 
> Patch 3 adjusts dot2c not to create lines over 100 columns
> 
> Patch 4 properly orders nested monitors in the RV Kconfig file

So keeping tools and kernel separate for RV is proving to be quite a
pain as patch 4 has conflicts. I'm going to make a third topic branch
just for RV. This will include anything in tools/verification and
kernel/trace/rv. I'll restructure the patches I already added and move
them into this branch, so that all the RV related work is there and not
in the latency or tools branches.

So no need to separate RV into kernel and tooling anymore.

> 
> Patch 5 returns the registration error in all DA monitor instead of 0
> 
> This series is based on the linux-next tree.

The topic branches I'll have is:

tools - for things like rtla
latency - for the latency tracers (osnoise, etc)
rv - for the runtime verification work.

-- Steve

  parent reply	other threads:[~2025-07-24 14:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23 16:12 [PATCH 0/5] tools/verification: Improvements to rv and rvgen Gabriele Monaco
2025-07-23 16:12 ` [PATCH 1/5] tools/rv: Do not skip idle in trace Gabriele Monaco
2025-07-23 16:12 ` [PATCH 2/5] tools/rv: Stop gracefully also on SIGTERM Gabriele Monaco
2025-07-23 16:12 ` [PATCH 3/5] tools/dot2c: Fix generated files going over 100 column limit Gabriele Monaco
2025-07-23 16:12 ` [PATCH 4/5] verification/rvgen: Organise Kconfig entries for nested monitors Gabriele Monaco
2025-07-23 16:12 ` [PATCH 5/5] rv: Return init error when registering monitors Gabriele Monaco
2025-07-24 14:40 ` Steven Rostedt [this message]
2025-07-24 18:07   ` [PATCH 0/5] tools/verification: Improvements to rv and rvgen Gabriele Monaco
2025-07-29 17:12     ` Steven Rostedt
2025-07-29 21:18 ` Steven Rostedt
2025-07-30  6:06   ` 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=20250724104011.7b4e11d9@batman.local.home \
    --to=rostedt@goodmis.org \
    --cc=gmonaco@redhat.com \
    --cc=jkacur@redhat.com \
    --cc=jlelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namcao@linutronix.de \
    --cc=tglozar@redhat.com \
    --cc=williams@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 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.