From: Tao Zhou <tao.zhou@linux.dev>
To: Daniel Bristot de Oliveira <bristot@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Jonathan Corbet <corbet@lwn.net>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Marco Elver <elver@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Gabriele Paoloni <gpaoloni@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Clark Williams <williams@redhat.com>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH V5 06/16] Documentation/rv: Add a basic documentation
Date: Sun, 17 Jul 2022 23:19:19 +0800 [thread overview]
Message-ID: <YtQodznMVSmwvhBr@geo.homenetwork> (raw)
In-Reply-To: <72d6b6619c9c336b254f5e560ac4ee5f44cb3956.1657745645.git.bristot@kernel.org>
On Wed, Jul 13, 2022 at 11:17:22PM +0200, Daniel Bristot de Oliveira wrote:
> Add the runtime-verification.rst document, explaining the basics of RV
> and how to use the interface.
>
> Cc: Wim Van Sebroeck <wim@linux-watchdog.org>
> Cc: Guenter Roeck <linux@roeck-us.net>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Will Deacon <will@kernel.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Marco Elver <elver@google.com>
> Cc: Dmitry Vyukov <dvyukov@google.com>
> Cc: "Paul E. McKenney" <paulmck@kernel.org>
> Cc: Shuah Khan <skhan@linuxfoundation.org>
> Cc: Gabriele Paoloni <gpaoloni@redhat.com>
> Cc: Juri Lelli <juri.lelli@redhat.com>
> Cc: Clark Williams <williams@redhat.com>
> Cc: Tao Zhou <tao.zhou@linux.dev>
> Cc: Randy Dunlap <rdunlap@infradead.org>
> Cc: linux-doc@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-trace-devel@vger.kernel.org
> Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
> ---
> Documentation/trace/index.rst | 1 +
> Documentation/trace/rv/index.rst | 9 +
> .../trace/rv/runtime-verification.rst | 233 ++++++++++++++++++
> kernel/trace/rv/Kconfig | 3 +
> kernel/trace/rv/rv.c | 3 +
> 5 files changed, 249 insertions(+)
> create mode 100644 Documentation/trace/rv/index.rst
> create mode 100644 Documentation/trace/rv/runtime-verification.rst
> + runtime-verification.rst
[snip]
> +The user interface
> +==================
> +
> +The user interface resembles the tracing interface (on purpose). It is
> +currently at "/sys/kernel/tracing/rv/".
> +
> +The following files/folders are currently available:
> +
> +**available_monitors**
> +
> +- Reading list the available monitors, one per line
> +
> +For example::
> +
> + # cat available_monitors
> + wip
> + wwnr
> +
> +**available_reactors**
> +
> +- Reading shows the available reactors, one per line.
> +
> +For example::
> +
> + # cat available_reactors
> + nop
> + panic
> + printk
> +
> +**enabled_monitors**:
> +
> +- Reading lists the enabled monitors, one per line
> +- Writing to it enables a given monitor
> +- Writing a monitor name with a '-' prefix disables it
s/-/!/
> +- Truncating the file disables all enabled monitors
> +
> +For example::
> +
> + # cat enabled_monitors
> + # echo wip > enabled_monitors
> + # echo wwnr >> enabled_monitors
> + # cat enabled_monitors
> + wip
> + wwnr
> + # echo '!wip' >> enabled_monitors
> + # cat enabled_monitors
> + wwnr
> + # echo > enabled_monitors
> + # cat enabled_monitors
> + #
> +
> +Note that it is possible to enable more than one monitor concurrently.
> +
> +
> +**monitoring_on**
> +
> +This is an on/off general switcher for monitoring. It resembles the
> +"tracing_on" switcher in the trace interface.
> +
> +- Writing "0" stops the monitoring
> +- Writing "1" continues the monitoring
> +- Reading returns the current status of the monitoring
> +
> +Note that it does not disable enabled monitors but stop the per-entity
> +monitors monitoring the events received from the system.
> +
> +**reacting_on**
> +
> +- Writing "0" prevents reactions for happening
> +- Writing "1" enable reactions
> +- Reading returns the current status of the monitoring
s/monitoring/reaction/
next prev parent reply other threads:[~2022-07-17 15:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 21:17 [PATCH V5 00/16] The Runtime Verification (RV) interface Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 01/16] rv: Add " Daniel Bristot de Oliveira
2022-07-14 7:46 ` Tao Zhou
2022-07-15 11:47 ` Daniel Bristot de Oliveira
2022-07-15 13:48 ` Tao Zhou
2022-07-13 21:17 ` [PATCH V5 02/16] rv: Add runtime reactors interface Daniel Bristot de Oliveira
2022-07-17 15:29 ` Tao Zhou
2022-07-17 18:56 ` kernel test robot
2022-07-13 21:17 ` [PATCH V5 03/16] rv/include: Add helper functions for deterministic automata Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 04/16] rv/include: Add deterministic automata monitor definition via C macros Daniel Bristot de Oliveira
2022-07-17 15:18 ` Tao Zhou
2022-07-18 7:54 ` Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 05/16] rv/include: Add instrumentation helper functions Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 06/16] Documentation/rv: Add a basic documentation Daniel Bristot de Oliveira
2022-07-17 15:19 ` Tao Zhou [this message]
2022-07-13 21:17 ` [PATCH V5 07/16] tools/rv: Add dot2c Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 08/16] Documentation/rv: Add deterministic automaton documentation Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 09/16] tools/rv: Add dot2k Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 10/16] Documentation/rv: Add deterministic automata monitor synthesis documentation Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 11/16] Documentation/rv: Add deterministic automata instrumentation documentation Daniel Bristot de Oliveira
2022-07-17 15:20 ` Tao Zhou
2022-07-13 21:17 ` [PATCH V5 12/16] rv/monitor: Add the wip monitor skeleton created by dot2k Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 13/16] rv/monitor: Add the wip monitor Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 14/16] rv/monitor: Add the wwnr monitor Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 15/16] rv/reactor: Add the printk reactor Daniel Bristot de Oliveira
2022-07-17 23:52 ` kernel test robot
2022-07-18 8:45 ` kernel test robot
2022-07-13 21:17 ` [PATCH V5 16/16] rv/reactor: Add the panic reactor Daniel Bristot de Oliveira
2022-07-18 2:05 ` kernel test robot
2022-07-18 11:50 ` kernel test robot
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=YtQodznMVSmwvhBr@geo.homenetwork \
--to=tao.zhou@linux.dev \
--cc=bristot@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=gpaoloni@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=williams@redhat.com \
--cc=wim@linux-watchdog.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