From: Philippe Gerum <rpm@xenomai.org>
To: Tobias Schaffner <tobias.schaffner@siemens.com>
Cc: xenomai@lists.linux.dev, jan.kiszka@siemens.com
Subject: Re: [RFC PATCH dovetail 0/7] rv: runtime verification monitors for Dovetail
Date: Thu, 19 Nov 2026 20:14:51 +0100 [thread overview]
Message-ID: <875wxsocpg.fsf@xenomai.org> (raw)
In-Reply-To: <20261110180847.633167-1-tobias.schaffner@siemens.com> (Tobias Schaffner's message of "Tue, 10 Nov 2026 19:08:40 +0100")
Tobias Schaffner <tobias.schaffner@siemens.com> writes:
> Hi all,
>
> with this RFC I would like to propose using the Linux kernel Runtime
> Verification (RV) system [1] for runtime verification of Dovetail based
> cokernels.
>
> Running a system with RV monitors active should ensure that the system
> behaves as described in the model. As this is checked at runtime we can
> verify if the system is even behaving as inteded when it is running the
> real workload.
>
> My ultimate goal is not only to use it for verification but also for wakeup
> latency tracing and decomposition in EVL by describing the whole wakeup
> path. I am working on upstreaming dwell time measurements in the RV system
> in parallel for that [2].
>
> This would allow us not only to get a worst case latency and decomposition
> for a latency evaluation tool like latmus but to get a worst case latency
> for any load applied to the system (e.g. the real application of the user).
>
> This patch set proposes three Dovetail monitors bundled in one container:
>
> * offstage checks that Linux leaves a task alone while it runs out-of-band. It
> must neither schedule the task nor let it raise a signal on itself.
>
> * oob_trap checks that every out-of-band trap notification is unwound for the
> same trap before the task goes out-of-band again.
>
> * oob_signal checks that a task receiving a signal out-of-band is kicked
> in-band. Once the cokernel handled the notification, the task must not return
> to user mode out-of-band without a mayday pending. I think his monitor found
> a present bug in EVL: since "evl/sched: get rid of this_evl_rq_thread()"
> evl_kick_thread() skips the mayday for a thread running out-of-band on a
> remote CPU, so the thread ignores all signals, even SIGKILL.
>
That one was bad indeed.
> For the monitors the series adds a few bare tracepoints to Dovetail. They are
> not exposed in tracefs.
>
> The monitors can be built by setting CONFIG_RV_DOVETAIL, which enables RV,
> the monitors and the printk reactor. oob_signal is not available on 32-bit
> arm yet, as the out-of-band syscall fast path there is written in assembly.
>
> To execute them:
>
> # cd /sys/kernel/tracing/rv
> # echo printk > monitors/dovetail/reactors
> # echo 1 > monitors/dovetail/enable
>
> Looking forward to your feedback, input and ideas on how to use and improve
> this further.
>
Did I already say this is insanely nice and useful work? Hopefully, I
did. I'm looking forward to merge RV support into the EVL core and
libevl.
--
Philippe.
prev parent reply other threads:[~2026-11-19 19:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 18:08 [RFC PATCH dovetail 0/7] rv: runtime verification monitors for Dovetail Tobias Schaffner
2026-11-10 18:08 ` [RFC PATCH dovetail 1/7] dovetail: factor out the mayday check on return to user mode Tobias Schaffner
2026-11-10 18:08 ` [RFC PATCH dovetail 2/7] dovetail: trace stage switches Tobias Schaffner
2026-11-11 7:40 ` Jan Kiszka
2026-11-19 19:07 ` Philippe Gerum
2026-11-10 18:08 ` [RFC PATCH dovetail 3/7] rv: add dovetail container and offstage monitor Tobias Schaffner
2026-11-10 18:08 ` [RFC PATCH dovetail 4/7] dovetail: trace out-of-band trap notifications Tobias Schaffner
2026-11-10 18:08 ` [RFC PATCH dovetail 5/7] rv: add oob_trap monitor Tobias Schaffner
2026-11-10 18:08 ` [RFC PATCH dovetail 6/7] dovetail: trace signal notifications and out-of-band returns Tobias Schaffner
2026-11-10 18:08 ` [RFC PATCH dovetail 7/7] rv: add oob_signal monitor Tobias Schaffner
2026-11-19 19:14 ` Philippe Gerum [this message]
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=875wxsocpg.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=jan.kiszka@siemens.com \
--cc=tobias.schaffner@siemens.com \
--cc=xenomai@lists.linux.dev \
/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.