From: Namhyung Kim <namhyung@kernel.org>
To: Tom Zanussi <tom.zanussi@linux.intel.com>
Cc: rostedt@goodmis.org, daniel.wagner@bmw-carit.de,
masami.hiramatsu.pt@hitachi.com, josh@joshtriplett.org,
andi@firstfloor.org, mathieu.desnoyers@efficios.com,
peterz@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v11 12/28] tracing: Add hist trigger support for user-defined sorting ('sort=' param)
Date: Mon, 2 Nov 2015 17:03:36 +0900 [thread overview]
Message-ID: <20151102080336.GD17941@sejong> (raw)
In-Reply-To: <ad381af401db7a07c43b512c102e26a6a7d4368f.1445530672.git.tom.zanussi@linux.intel.com>
On Thu, Oct 22, 2015 at 01:14:16PM -0500, Tom Zanussi wrote:
> Allow users to specify keys and/or values to sort on. With this
> addition, keys and values specified using the 'keys=' and 'vals='
> keywords can be used to sort the hist trigger output via a new 'sort='
> keyword. If multiple sort keys are specified, the output will be
> sorted using the second key as a secondary sort key, etc. The default
> sort order is ascending; if the user wants a different sort order,
> '.descending' can be appended to the specific sort key. Before this
> addition, output was always sorted by 'hitcount' in ascending order.
>
> This expands the hist trigger syntax from this:
>
> # echo hist:keys=xxx:vals=yyy \
> [ if filter] > event/trigger
>
> to this:
>
> # echo hist:keys=xxx:vals=yyy:sort=zzz.descending \
> [ if filter] > event/trigger
>
> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
> Tested-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
> ---
[SNIP]
> static int create_sort_keys(struct hist_trigger_data *hist_data)
> {
> + char *fields_str = hist_data->attrs->sort_key_str;
> + struct ftrace_event_field *field = NULL;
> + struct tracing_map_sort_key *sort_key;
> + unsigned int i, j;
> int ret = 0;
>
> hist_data->n_sort_keys = 1; /* sort_keys[0] is always hitcount */
This comment should be updated.
Thanks,
Namhyung
>
> + if (!fields_str)
> + goto out;
> +
> + strsep(&fields_str, "=");
> + if (!fields_str) {
> + ret = -EINVAL;
> + goto out;
> + }
> +
> + for (i = 0; i < TRACING_MAP_SORT_KEYS_MAX; i++) {
> + char *field_str, *field_name;
> +
> + sort_key = &hist_data->sort_keys[i];
> +
> + field_str = strsep(&fields_str, ",");
> + if (!field_str) {
> + if (i == 0)
> + ret = -EINVAL;
> + break;
> + }
> +
> + if ((i == TRACING_MAP_SORT_KEYS_MAX - 1) && fields_str) {
> + ret = -EINVAL;
> + break;
> + }
> +
> + field_name = strsep(&field_str, ".");
> + if (!field_name) {
> + ret = -EINVAL;
> + break;
> + }
> +
> + if (!strcmp(field_name, "hitcount")) {
> + ret = is_descending(field_str);
> + if (ret < 0)
> + break;
> + sort_key->descending = ret;
> + continue;
> + }
> +
> + for (j = 1; j < hist_data->n_fields; j++) {
> + field = hist_data->fields[j]->field;
> + if (field && !strcmp(field_name, field->name)) {
> + sort_key->field_idx = j;
> + ret = is_descending(field_str);
> + if (ret < 0)
> + goto out;
> + sort_key->descending = ret;
> + break;
> + }
> + }
> + if (j == hist_data->n_fields) {
> + ret = -EINVAL;
> + break;
> + }
> + }
> + hist_data->n_sort_keys = i;
> + out:
> return ret;
> }
>
> @@ -737,7 +817,26 @@ static int event_hist_trigger_print(struct seq_file *m,
> }
>
> seq_puts(m, ":sort=");
> - seq_puts(m, "hitcount");
> +
> + for (i = 0; i < hist_data->n_sort_keys; i++) {
> + struct tracing_map_sort_key *sort_key;
> +
> + sort_key = &hist_data->sort_keys[i];
> +
> + if (i > 0)
> + seq_puts(m, ",");
> +
> + if (sort_key->field_idx == HITCOUNT_IDX)
> + seq_puts(m, "hitcount");
> + else {
> + unsigned int idx = sort_key->field_idx;
> +
> + hist_field_print(m, hist_data->fields[idx]);
> + }
> +
> + if (sort_key->descending)
> + seq_puts(m, ".descending");
> + }
>
> seq_printf(m, ":size=%u", (1 << hist_data->map->map_bits));
>
> --
> 1.9.3
>
next prev parent reply other threads:[~2015-11-02 8:03 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 18:14 [PATCH 00/28] tracing: 'hist' triggers Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 01/28] tracing: Update cond flag when enabling or disabling a trigger Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 02/28] tracing: Make ftrace_event_field checking functions available Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 03/28] tracing: Make event trigger " Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 04/28] tracing: Add event record param to trigger_ops.func() Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 05/28] tracing: Add get_syscall_name() Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 06/28] tracing: Add a per-event-trigger 'paused' field Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 07/28] tracing: Add needs_rec flag to event triggers Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 08/28] tracing: Add lock-free tracing_map Tom Zanussi
2015-10-29 8:31 ` Namhyung Kim
2015-10-29 18:35 ` Tom Zanussi
2015-11-02 7:08 ` Namhyung Kim
2015-11-04 1:47 ` Tom Zanussi
2015-11-04 2:26 ` Namhyung Kim
2015-11-04 2:56 ` Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 09/28] tracing: Add 'hist' event trigger command Tom Zanussi
2015-10-29 9:11 ` Namhyung Kim
2015-10-29 18:37 ` Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 10/28] tracing: Add hist trigger support for multiple values ('vals=' param) Tom Zanussi
2015-11-02 7:42 ` Namhyung Kim
2015-10-22 18:14 ` [PATCH v11 11/28] tracing: Add hist trigger support for compound keys Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 12/28] tracing: Add hist trigger support for user-defined sorting ('sort=' param) Tom Zanussi
2015-11-02 8:03 ` Namhyung Kim [this message]
2015-10-22 18:14 ` [PATCH v11 13/28] tracing: Add hist trigger support for pausing and continuing a trace Tom Zanussi
2015-11-03 8:38 ` Namhyung Kim
2015-11-04 1:53 ` Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 14/28] tracing: Add hist trigger support for clearing " Tom Zanussi
2015-11-03 8:43 ` Namhyung Kim
2015-10-22 18:14 ` [PATCH v11 15/28] tracing: Add hist trigger 'hex' modifier for displaying numeric fields Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 16/28] tracing: Add hist trigger 'sym' and 'sym-offset' modifiers Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 17/28] tracing: Add hist trigger 'execname' modifier Tom Zanussi
2015-11-02 14:10 ` Namhyung Kim
2015-11-04 2:37 ` Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 18/28] tracing: Add hist trigger 'syscall' modifier Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 19/28] tracing: Add hist trigger support for stacktraces as keys Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 20/28] tracing: Support string type key properly Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 21/28] tracing: Remove restriction on string position in hist trigger keys Tom Zanussi
2015-11-02 14:40 ` Namhyung Kim
2015-10-22 18:14 ` [PATCH v11 22/28] tracing: Add enable_hist/disable_hist triggers Tom Zanussi
2015-11-03 8:55 ` Namhyung Kim
2015-11-04 1:58 ` Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 23/28] tracing: Add 'hist' trigger Documentation Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 24/28] tracing: Add support for multiple hist triggers per event Tom Zanussi
2015-11-03 0:34 ` Namhyung Kim
2015-11-04 1:52 ` Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 25/28] tracing: Add support for named triggers Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 26/28] tracing: Add support for named hist triggers Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 27/28] kselftests/ftrace : Add event trigger testcases Tom Zanussi
2015-10-22 18:14 ` [PATCH v11 28/28] kselftests/ftrace: Add hist " Tom Zanussi
2015-10-22 18:21 ` [PATCH 00/28] tracing: 'hist' triggers Steven Rostedt
2015-10-22 18:31 ` Tom Zanussi
2015-11-05 14:43 ` Namhyung Kim
2015-11-05 14:59 ` 平松雅巳 / HIRAMATU,MASAMI
2015-11-05 22:13 ` Tom Zanussi
2015-11-05 23:18 ` Namhyung Kim
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=20151102080336.GD17941@sejong \
--to=namhyung@kernel.org \
--cc=andi@firstfloor.org \
--cc=daniel.wagner@bmw-carit.de \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tom.zanussi@linux.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;
as well as URLs for NNTP newsgroup(s).