From: Namhyung Kim <namhyung@kernel.org>
To: Tom Zanussi <tom.zanussi@linux.intel.com>
Cc: rostedt@goodmis.org, tglx@linutronix.de, mhiramat@kernel.org,
vedang.patel@intel.com, bigeasy@linutronix.de,
joel.opensrc@gmail.com, joelaf@google.com,
mathieu.desnoyers@efficios.com, baohong.liu@intel.com,
rajvi.jingar@intel.com, julia@ni.com,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
kernel-team@lge.com
Subject: Re: [PATCH v5 15/37] tracing: Add variable support to hist triggers
Date: Fri, 10 Nov 2017 16:28:41 +0900 [thread overview]
Message-ID: <20171110072841.GB1544@danjae.aot.lge.com> (raw)
In-Reply-To: <d9fc474596939557a4db9adb92eec65bd2283131.1510252666.git.tom.zanussi@linux.intel.com>
Hi Tom,
On Thu, Nov 09, 2017 at 02:33:46PM -0600, Tom Zanussi wrote:
> Add support for saving the value of a current event's event field by
> assigning it to a variable that can be read by a subsequent event.
>
> The basic syntax for saving a variable is to simply prefix a unique
> variable name not corresponding to any keyword along with an '=' sign
> to any event field.
>
> Both keys and values can be saved and retrieved in this way:
>
> # echo 'hist:keys=next_pid:vals=$ts0:ts0=$common_timestamp ...
> # echo 'hist:timer_pid=common_pid:key=$timer_pid ...'
>
> If a variable isn't a key variable or prefixed with 'vals=', the
> associated event field will be saved in a variable but won't be summed
> as a value:
>
> # echo 'hist:keys=next_pid:ts1=$common_timestamp:...
>
> Multiple variables can be assigned at the same time:
>
> # echo 'hist:keys=pid:vals=$ts0,$b,field2:ts0=$common_timestamp,b=field1 ...
>
> Multiple (or single) variables can also be assigned at the same time
> using separate assignments:
>
> # echo 'hist:keys=pid:vals=$ts0:ts0=$common_timestamp:b=field1:c=field2 ...
>
> Variables set as above can be used by being referenced from another
> event, as described in a subsequent patch.
>
> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
> Signed-off-by: Baohong Liu <baohong.liu@intel.com>
> ---
[SNIP]
> +static int parse_var_defs(struct hist_trigger_data *hist_data)
> +{
> + char *s, *str, *var_name, *field_str;
> + unsigned int i, j, n_vars = 0;
> + int ret = 0;
> +
> + for (i = 0; i < hist_data->attrs->n_assignments; i++) {
> + str = hist_data->attrs->assignment_str[i];
> + for (j = 0; j < TRACING_MAP_VARS_MAX; j++) {
> + field_str = strsep(&str, ",");
> + if (!field_str)
> + break;
> +
> + var_name = strsep(&field_str, "=");
> + if (!var_name || !field_str) {
> + ret = -EINVAL;
> + goto free;
> + }
> +
> + s = kstrdup(var_name, GFP_KERNEL);
> + if (!s) {
> + ret = -ENOMEM;
> + goto free;
> + }
> + hist_data->attrs->var_defs.name[n_vars] = s;
> +
> + s = kstrdup(field_str, GFP_KERNEL);
> + if (!s) {
> + kfree(hist_data->attrs->var_defs.name[n_vars]);
> + ret = -ENOMEM;
> + goto free;
> + }
> + hist_data->attrs->var_defs.expr[n_vars++] = s;
> +
> + hist_data->attrs->var_defs.n_vars = n_vars;
> +
> + if (n_vars == TRACING_MAP_VARS_MAX)
> + goto free;
This will silently discard all variables. Why not returning an error?
Also I think it should be moved to the beginning of this block..
Thanks,
Namhyung
> + }
> + }
> +
> + return ret;
> + free:
> + free_var_defs(hist_data);
> +
> + return ret;
> +}
next prev parent reply other threads:[~2017-11-10 7:31 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 20:33 [PATCH v5 00/37] tracing: Inter-event (e.g. latency) support Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 01/37] tracing: Move hist trigger Documentation to histogram.txt Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 02/37] tracing: Add Documentation for log2 modifier Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 03/37] tracing: Add support to detect and avoid duplicates Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 04/37] tracing: Remove code which merges duplicates Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 05/37] ring-buffer: Add interface for setting absolute time stamps Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 06/37] ring-buffer: Redefine the unimplemented RINGBUF_TYPE_TIME_STAMP Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 07/37] tracing: Add timestamp_mode trace file Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 08/37] tracing: Give event triggers access to ring_buffer_event Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 09/37] tracing: Add ring buffer event param to hist field functions Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 10/37] tracing: Break out hist trigger assignment parsing Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 11/37] tracing: Add hist trigger timestamp support Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 12/37] tracing: Add per-element variable support to tracing_map Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 13/37] tracing: Add hist_data member to hist_field Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 14/37] tracing: Add usecs modifier for hist trigger timestamps Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 15/37] tracing: Add variable support to hist triggers Tom Zanussi
2017-11-10 7:28 ` Namhyung Kim [this message]
2017-11-10 13:24 ` Steven Rostedt
2017-11-10 16:26 ` Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 16/37] tracing: Account for variables in named trigger compatibility Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 17/37] tracing: Move get_hist_field_flags() Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 18/37] tracing: Add simple expression support to hist triggers Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 19/37] tracing: Generalize per-element hist trigger data Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 20/37] tracing: Pass tracing_map_elt to hist_field accessor functions Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 21/37] tracing: Add hist_field 'type' field Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 22/37] tracing: Add variable reference handling to hist triggers Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 23/37] tracing: Add hist trigger action hook Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 24/37] tracing: Add support for 'synthetic' events Tom Zanussi
2017-11-14 1:21 ` Namhyung Kim
2017-11-14 19:24 ` Tom Zanussi
2017-11-14 10:06 ` Namhyung Kim
2017-11-14 19:34 ` Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 25/37] tracing: Add support for 'field variables' Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 26/37] tracing: Add 'onmatch' hist trigger action support Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 27/37] tracing: Add 'onmax' " Tom Zanussi
2017-11-09 20:33 ` [PATCH v5 28/37] tracing: Allow whitespace to surround hist trigger filter Tom Zanussi
2017-11-09 20:34 ` [PATCH v5 29/37] tracing: Add cpu field for hist triggers Tom Zanussi
2017-11-09 20:34 ` [PATCH v5 30/37] tracing: Add hist trigger support for variable reference aliases Tom Zanussi
2017-11-09 20:34 ` [PATCH v5 31/37] tracing: Add 'last error' error facility for hist triggers Tom Zanussi
2017-11-09 20:34 ` [PATCH v5 32/37] tracing: Add inter-event hist trigger Documentation Tom Zanussi
2017-11-09 20:34 ` [PATCH v5 33/37] tracing: Make tracing_set_clock() non-static Tom Zanussi
2017-11-09 20:34 ` [PATCH v5 34/37] tracing: Add a clock attribute for hist triggers Tom Zanussi
2017-11-09 20:34 ` [PATCH v5 35/37] tracing: Increase trace_recursive_lock() limit for synthetic events Tom Zanussi
2017-11-09 20:34 ` [PATCH v5 36/37] tracing: Add inter-event blurb to HIST_TRIGGERS config option Tom Zanussi
2017-11-09 20:34 ` [PATCH v5 37/37] selftests: ftrace: Add inter-event hist triggers testcases Tom Zanussi
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=20171110072841.GB1544@danjae.aot.lge.com \
--to=namhyung@kernel.org \
--cc=baohong.liu@intel.com \
--cc=bigeasy@linutronix.de \
--cc=joel.opensrc@gmail.com \
--cc=joelaf@google.com \
--cc=julia@ni.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rajvi.jingar@intel.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.com \
--cc=vedang.patel@intel.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
Powered by JetHome