From: Masami Hiramatsu <mhiramat@kernel.org>
To: Kalesh Singh <kaleshsingh@google.com>
Cc: surenb@google.com, hridya@google.com, namhyung@kernel.org,
kernel-team@android.com, rostedt@goodmis.org,
mhiramat@kernel.org, Ingo Molnar <mingo@redhat.com>,
Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 1/3] tracing/histogram: Document hist trigger variables
Date: Thu, 28 Oct 2021 07:13:19 +0900 [thread overview]
Message-ID: <20211028071319.44e3e885352866713dd08046@kernel.org> (raw)
In-Reply-To: <20211027205919.1648553-2-kaleshsingh@google.com>
On Wed, 27 Oct 2021 13:59:08 -0700
Kalesh Singh <kaleshsingh@google.com> wrote:
> Update the tracefs README to describe how hist trigger variables
> can be created.
>
> Signed-off-by: Kalesh Singh <kaleshsingh@google.com>
This looks good to me.
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Thank you!
> ---
> kernel/trace/trace.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index bc677cd64224..c41b3786401d 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -5628,6 +5628,7 @@ static const char readme_msg[] =
> #ifdef CONFIG_HIST_TRIGGERS
> " hist trigger\t- If set, event hits are aggregated into a hash table\n"
> "\t Format: hist:keys=<field1[,field2,...]>\n"
> + "\t [:<var1>=<field|var_ref|numeric_literal>[,<var2>=...]]\n"
> "\t [:values=<field1[,field2,...]>]\n"
> "\t [:sort=<field1[,field2,...]>]\n"
> "\t [:size=#entries]\n"
> @@ -5639,6 +5640,16 @@ static const char readme_msg[] =
> "\t common_timestamp - to record current timestamp\n"
> "\t common_cpu - to record the CPU the event happened on\n"
> "\n"
> + "\t A hist trigger variable can be:\n"
> + "\t - a reference to a field e.g. x=current_timestamp,\n"
> + "\t - a reference to another variable e.g. y=$x,\n"
> + "\t - a numeric literal: e.g. ms_per_sec=1000,\n"
> + "\t - an arithmetic expression: e.g. time_secs=current_timestamp/1000\n"
> + "\n"
> + "\t hist trigger aritmethic expressions support addition(+), subtraction(-),\n"
> + "\t multiplication(*) and division(/) operators. An operand can be either a\n"
> + "\t variable reference, field or numeric literal.\n"
> + "\n"
> "\t When a matching event is hit, an entry is added to a hash\n"
> "\t table using the key(s) and value(s) named, and the value of a\n"
> "\t sum called 'hitcount' is incremented. Keys and values\n"
> --
> 2.33.0.1079.g6e70778dc9-goog
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2021-10-27 22:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 20:59 [PATCH 0/3] tracing/kselftest: histogram trigger expression tests Kalesh Singh
2021-10-27 20:59 ` [PATCH 1/3] tracing/histogram: Document hist trigger variables Kalesh Singh
2021-10-27 22:13 ` Masami Hiramatsu [this message]
2021-10-27 20:59 ` [PATCH 2/3] tracing/kselftests: Remove triggers with references before their definitions Kalesh Singh
2021-10-27 21:58 ` Masami Hiramatsu
2021-10-27 23:26 ` Kalesh Singh
2021-10-27 23:54 ` Steven Rostedt
2021-10-28 0:43 ` Masami Hiramatsu
2021-10-28 2:58 ` Kalesh Singh
2021-10-28 17:10 ` Kalesh Singh
2021-10-27 20:59 ` [PATCH v5 3/3] tracing/selftests: Add tests for hist trigger expression parsing Kalesh Singh
2021-10-27 22:12 ` Masami Hiramatsu
2021-10-27 21:04 ` [PATCH 0/3] tracing/kselftest: histogram trigger expression tests Kalesh Singh
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=20211028071319.44e3e885352866713dd08046@kernel.org \
--to=mhiramat@kernel.org \
--cc=hridya@google.com \
--cc=kaleshsingh@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
/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
all inboxes | Powered by JetHome®