Linux Trace Development
 help / color / mirror / Atom feed
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, Tao Zhou <tao.zhou@linux.dev>
Subject: Re: [PATCH V6 11/16] Documentation/rv: Add deterministic automata instrumentation documentation
Date: Thu, 21 Jul 2022 22:57:12 +0800	[thread overview]
Message-ID: <YtlpSGp590YJXT22@geo.homenetwork> (raw)
In-Reply-To: <3c915ffd00f033d57dbac2f69e56a87b7b80adba.1658244826.git.bristot@kernel.org>

On Tue, Jul 19, 2022 at 07:27:16PM +0200, Daniel Bristot de Oliveira wrote:

> +Looking at the automata definition, it is possible to see that the system
> +and the model are expected to return to the initial state after the
> +preempt_enable execution. Hence, it can be used to synchronize the
> +system and the model at the initialization of the monitoring section.
> +
> +The start is informed via a special handle function, the
> +"da_handle_start_event_MONITOR_event)", in this case::

da_handle_start_event_$MONITOR(event) the same as the previous version
should be right.

> +
> +  da_handle_start_event_wip(preempt_disable_wip);

I didn't see this in last version that the event should be preempt_enable_wip.

> +
> +So, the callback function will look like::
> +
> +  void handle_preempt_enable(void *data, unsigned long ip, unsigned long parent_ip)
> +  {
> +        da_handle_start_event_wip(preempt_enable_wip);
> +  }
> +
> +Finally, the "handle_sched_waking()" will look like::
> +
> +  void handle_sched_waking(void *data, struct task_struct *task)
> +  {
> +        da_handle_event_wip(sched_waking_wip);
> +  }
> +
> +And the explanation is left for the reader as an exercise.
> +
> +Start and Stop functions

Start and Stop functions are changed to enable and disable functions.

> +------------------------
> +
> +dot2k automatically creates two special functions::
> +
> +  enable_MONITOR()
> +  disable_MONITOR()
> +
> +These functions are called when the monitor is enabled and disabled,
> +respectively.
> +
> +They should be used to *attach* and *detach* the instrumentation to the running
> +system. The developer must add to the relative function all that is needed to
> +*attach* and *detach* its monitor to the system.
> +
> +For the wip case, these functions were named::
> +
> + enable_wip()
> + disable_wip()
> +
> +But no change was required because: by default, these functions *attach* and
> +*detach* the tracepoints_to_attach, which was enough for this case.

  reply	other threads:[~2022-07-21 14:57 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 17:27 [PATCH V6 00/16] The Runtime Verification (RV) interface Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 01/16] rv: Add " Daniel Bristot de Oliveira
2022-07-20 14:47   ` Steven Rostedt
2022-07-20 15:20     ` Daniel Bristot de Oliveira
2022-07-20 15:21   ` Steven Rostedt
2022-07-20 15:33     ` Daniel Bristot de Oliveira
2022-07-21 14:38   ` Tao Zhou
2022-07-21 14:54     ` Steven Rostedt
2022-07-19 17:27 ` [PATCH V6 02/16] rv: Add runtime reactors interface Daniel Bristot de Oliveira
2022-07-20 16:41   ` Steven Rostedt
2022-07-20 16:50     ` Daniel Bristot de Oliveira
2022-07-20 17:02       ` Steven Rostedt
2022-07-20 17:37         ` Daniel Bristot de Oliveira
2022-07-20 17:45           ` Steven Rostedt
2022-07-21 14:46   ` Tao Zhou
2022-07-19 17:27 ` [PATCH V6 03/16] rv/include: Add helper functions for deterministic automata Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 04/16] rv/include: Add deterministic automata monitor definition via C macros Daniel Bristot de Oliveira
2022-07-20 20:06   ` Steven Rostedt
2022-07-21 12:08     ` Daniel Bristot de Oliveira
2022-07-21 13:59       ` Steven Rostedt
2022-07-21 16:38         ` Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 05/16] rv/include: Add instrumentation helper functions Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 06/16] Documentation/rv: Add a basic documentation Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 07/16] tools/rv: Add dot2c Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 08/16] Documentation/rv: Add deterministic automaton documentation Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 09/16] tools/rv: Add dot2k Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 10/16] Documentation/rv: Add deterministic automata monitor synthesis documentation Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 11/16] Documentation/rv: Add deterministic automata instrumentation documentation Daniel Bristot de Oliveira
2022-07-21 14:57   ` Tao Zhou [this message]
2022-07-19 17:27 ` [PATCH V6 12/16] rv/monitor: Add the wip monitor skeleton created by dot2k Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 13/16] rv/monitor: Add the wip monitor Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 14/16] rv/monitor: Add the wwnr monitor Daniel Bristot de Oliveira
2022-07-24 18:12   ` kernel test robot
2022-07-19 17:27 ` [PATCH V6 15/16] rv/reactor: Add the printk reactor Daniel Bristot de Oliveira
2022-07-21 15:29   ` Steven Rostedt
2022-07-19 17:27 ` [PATCH V6 16/16] rv/reactor: Add the panic reactor Daniel Bristot de Oliveira
2022-07-21 15:31   ` Steven Rostedt
2022-07-21 16:43     ` Daniel Bristot de Oliveira

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=YtlpSGp590YJXT22@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