linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nam Cao <namcao@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>,
	John Ogness <john.ogness@linutronix.de>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Gabriele Monaco <gmonaco@redhat.com>,
	linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Nam Cao <namcao@linutronix.de>
Subject: [PATCH 0/2] rv/ltl: Support the 'next' operator
Date: Fri, 11 Jul 2025 15:17:36 +0200	[thread overview]
Message-ID: <cover.1752239482.git.namcao@linutronix.de> (raw)

Hi,

In the theory of linear temporal logic, there is also the 'next' unary
operator defined as: next time, the operand must be true.

During my initial implementation, I thought kernel RV monitors would not
have a use case for this operator. Therefore I omitted it.

However, me and Gabriele had a conversion off list, and he may have a use
case for this operator.

Therefore, implement the theory completely and add the 'next' operator.

Nam Cao (2):
  rv/ltl: Do not execute the Buchi automaton twice on start condition
  verification/rvgen: Support the 'next' operator

 .../trace/rv/linear_temporal_logic.rst        |  1 +
 include/rv/ltl_monitor.h                      |  4 ++-
 tools/verification/rvgen/rvgen/ltl2ba.py      | 26 +++++++++++++++++++
 3 files changed, 30 insertions(+), 1 deletion(-)

-- 
2.39.5


             reply	other threads:[~2025-07-11 13:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11 13:17 Nam Cao [this message]
2025-07-11 13:17 ` [PATCH 1/2] rv/ltl: Do not execute the Buchi automaton twice on start condition Nam Cao
2025-07-11 13:17 ` [PATCH 2/2] verification/rvgen: Support the 'next' operator Nam Cao
2025-07-14 12:18   ` Gabriele Monaco
2025-07-14 12:42     ` Nam Cao
2025-07-14 12:48       ` Nam Cao
2025-07-14 12:50         ` Nam Cao
2025-07-14 13:56         ` 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=cover.1752239482.git.namcao@linutronix.de \
    --to=namcao@linutronix.de \
    --cc=gmonaco@redhat.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).