From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>, linux-trace-devel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] tools/rv: Add in-kernel monitor interface
Date: Wed, 26 Oct 2022 14:31:07 +0200 [thread overview]
Message-ID: <dec2d423-9f22-e172-abe7-29a9dad8cf12@kernel.org> (raw)
In-Reply-To: <d52a15b93acb15142551b8e84ff4bcd934de22ce.1666776642.git.bristot@kernel.org>
On 10/26/22 12:44, Daniel Bristot de Oliveira wrote:
> Add the ability to control and trace in-kernel monitors. This is
> a generic interface, it will check for existing monitors and enable
> standard setup, like enabling reactors.
Oops, forgot to add spaces before #
> For example:
>
# rv list
> wip wakeup in preemptive per-cpu testing monitor. [OFF]
> wwnr wakeup while not running per-task testing model. [OFF]
# rv mon wip --help
>
> help:
>
> usage: rv mon wwnr [-h] [-q] [-r reactor] [-s] [-v]
> -h/--help: print this menu and the reactor list
> -r/--reactor 'reactor': enables the 'reactor'
> -s/--self: when tracing (-t), also trace rv command
> -t/--trace: trace monitor's event
> -v/--verbose: print debug messages
>
> available reactors: nop printk panic
# rv mon wip --trace
> <TASK>-PID [CPU] TYPE ID STATE x EVENT -> NEXT_STATE FINAL
> | | | | | | | | |
> rv-3613 [001] event 3613 running x switch_out -> not_running Y
> sshd-1248 [005] event 1248 running x switch_out -> not_running Y
> <idle>-0 [005] event 71 not_running x wakeup -> not_running Y
> <idle>-0 [005] event 71 not_running x switch_in -> running N
> kcompactd0-71 [005] event 71 running x switch_out -> not_running Y
> <idle>-0 [000] event 860 not_running x wakeup -> not_running Y
> <idle>-0 [000] event 860 not_running x switch_in -> running N
> systemd-oomd-860 [000] event 860 running x switch_out -> not_running Y
> <idle>-0 [000] event 860 not_running x wakeup -> not_running Y
> <idle>-0 [000] event 860 not_running x switch_in -> running N
> systemd-oomd-860 [000] event 860 running x switch_out -> not_running Y
> <idle>-0 [005] event 71 not_running x wakeup -> not_running Y
> <idle>-0 [005] event 71 not_running x switch_in -> running N
> kcompactd0-71 [005] event 71 running x switch_out -> not_running Y
> <idle>-0 [000] event 860 not_running x wakeup -> not_running Y
> <idle>-0 [000] event 860 not_running x switch_in -> running N
> systemd-oomd-860 [000] event 860 running x switch_out -> not_running Y
> <idle>-0 [001] event 3613 not_running x wakeup -> not_running Y
>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
I will fix this log to in the next version.
-- Daniel
next prev parent reply other threads:[~2022-10-26 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 10:44 [PATCH 0/3] verification/rv: Add rv tool Daniel Bristot de Oliveira
2022-10-26 10:44 ` [PATCH 1/3] rv: " Daniel Bristot de Oliveira
2022-10-26 10:44 ` [PATCH 2/3] tools/rv: Add in-kernel monitor interface Daniel Bristot de Oliveira
2022-10-26 12:31 ` Daniel Bristot de Oliveira [this message]
2022-10-26 10:44 ` [PATCH 3/3] Documentation/rv: Add verification/rv man pages 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=dec2d423-9f22-e172-abe7-29a9dad8cf12@kernel.org \
--to=bristot@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.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 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.