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, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 14/22] tracing: Add hist trigger 'hex' modifier for displaying numeric fields
Date: Sun, 19 Jul 2015 22:22:33 +0900 [thread overview]
Message-ID: <20150719132233.GD25163@danjae.kornet> (raw)
In-Reply-To: <e837047664efb2cf934508a102b065cefa7c5d4b.1437066836.git.tom.zanussi@linux.intel.com>
Hi Tom,
On Thu, Jul 16, 2015 at 12:22:47PM -0500, Tom Zanussi wrote:
> Allow users to have numeric fields displayed as hex values in the
> output by appending '.hex' to field names:
>
> # echo hist:keys=aaa,bbb.hex:vals=ccc.hex ... \
> [ if filter] > event/trigger
>
> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
> ---
> kernel/trace/trace.c | 5 +++-
> kernel/trace/trace_events_hist.c | 49 +++++++++++++++++++++++++++++++++++++---
> 2 files changed, 50 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index 27daa28..14f9472 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -3810,7 +3810,10 @@ static const char readme_msg[] =
> "\t entry is a simple list of the keys and values comprising the\n"
> "\t entry; keys are printed first and are delineated by curly\n"
> "\t braces, and are followed by the set of value fields for the\n"
> - "\t entry. Numeric fields are displayed as base-10 integers.\n"
> + "\t entry. By default, numeric fields are displayed as base-10\n"
> + "\t integers. This can be modified by appending any of the\n"
> + "\t following modifiers to the field name:\n\n"
> + "\t .hex display a number as a hex value\n\n"
> "\t By default, the size of the hash table is 2048 entries. The\n"
> "\t 'size' param can be used to specify more or fewer than that.\n"
> "\t The units are in terms of hashtable entries - if a run uses\n"
> diff --git a/kernel/trace/trace_events_hist.c b/kernel/trace/trace_events_hist.c
> index d8259fe..9cc38ee 100644
> --- a/kernel/trace/trace_events_hist.c
> +++ b/kernel/trace/trace_events_hist.c
> @@ -72,6 +72,7 @@ enum hist_field_flags {
> HIST_FIELD_HITCOUNT = 1,
> HIST_FIELD_KEY = 2,
> HIST_FIELD_STRING = 4,
> + HIST_FIELD_HEX = 8,
> };
>
> struct hist_trigger_attrs {
> @@ -284,9 +285,20 @@ static int create_val_field(struct hist_trigger_data *hist_data,
> {
> struct ftrace_event_field *field = NULL;
> unsigned long flags = 0;
> + char *field_name;
> int ret = 0;
>
> - field = trace_find_event_field(file->event_call, field_str);
> + field_name = strsep(&field_str, ".");
> + if (field_str) {
> + if (!strcmp(field_str, "hex"))
> + flags |= HIST_FIELD_HEX;
> + else {
> + ret = -EINVAL;
> + goto out;
> + }
> + }
> +
> + field = trace_find_event_field(file->event_call, field_name);
> if (!field) {
> ret = -EINVAL;
> goto out;
> @@ -349,11 +361,22 @@ static int create_key_field(struct hist_trigger_data *hist_data,
> struct ftrace_event_field *field = NULL;
> unsigned long flags = 0;
> unsigned int key_size;
> + char *field_name;
> int ret = 0;
>
> flags |= HIST_FIELD_KEY;
>
> - field = trace_find_event_field(file->event_call, field_str);
> + field_name = strsep(&field_str, ".");
> + if (field_str) {
> + if (!strcmp(field_str, "hex"))
> + flags |= HIST_FIELD_HEX;
> + else {
> + ret = -EINVAL;
> + goto out;
> + }
> + }
> +
> + field = trace_find_event_field(file->event_call, field_name);
> if (!field) {
> ret = -EINVAL;
> goto out;
> @@ -688,7 +711,11 @@ hist_trigger_entry_print(struct seq_file *m,
> if (i > hist_data->n_vals)
> seq_puts(m, ", ");
>
> - if (key_field->flags & HIST_FIELD_STRING) {
> + if (key_field->flags & HIST_FIELD_HEX) {
> + uval = *(u64 *)(key + key_field->offset);
> + seq_printf(m, "%s: %llx",
> + key_field->field->name, uval);
> + } else if (key_field->flags & HIST_FIELD_STRING) {
> seq_printf(m, "%s: %-35s", key_field->field->name,
> (char *)(key + key_field->offset));
> } else {
It seems the '.hex' modifier only affects key fields' output..
Thanks,
Namhyung
> @@ -791,9 +818,25 @@ const struct file_operations event_hist_fops = {
> .release = single_release,
> };
>
> +static const char *get_hist_field_flags(struct hist_field *hist_field)
> +{
> + const char *flags_str = NULL;
> +
> + if (hist_field->flags & HIST_FIELD_HEX)
> + flags_str = "hex";
> +
> + return flags_str;
> +}
> +
> static void hist_field_print(struct seq_file *m, struct hist_field *hist_field)
> {
> seq_printf(m, "%s", hist_field->field->name);
> + if (hist_field->flags) {
> + const char *flags_str = get_hist_field_flags(hist_field);
> +
> + if (flags_str)
> + seq_printf(m, ".%s", flags_str);
> + }
> }
>
> static int event_hist_trigger_print(struct seq_file *m,
> --
> 1.9.3
>
next prev parent reply other threads:[~2015-07-19 13:24 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 17:22 [PATCH v9 00/22] tracing: 'hist' triggers Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 01/22] tracing: Update cond flag when enabling or disabling a trigger Tom Zanussi
2015-07-21 10:04 ` Masami Hiramatsu
2015-07-16 17:22 ` [PATCH v9 02/22] tracing: Make ftrace_event_field checking functions available Tom Zanussi
2015-07-21 10:04 ` Masami Hiramatsu
2015-07-21 14:26 ` Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 03/22] tracing: Make event trigger " Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 04/22] tracing: Add event record param to trigger_ops.func() Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 05/22] tracing: Add get_syscall_name() Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 06/22] tracing: Add a per-event-trigger 'paused' field Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 07/22] tracing: Add lock-free tracing_map Tom Zanussi
2015-07-16 17:49 ` Peter Zijlstra
2015-07-16 21:41 ` Tom Zanussi
2015-07-16 22:32 ` Peter Zijlstra
2015-07-17 1:51 ` Tom Zanussi
2015-07-16 18:03 ` Peter Zijlstra
2015-07-16 21:33 ` Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 08/22] tracing: Add 'hist' event trigger command Tom Zanussi
2015-07-20 13:37 ` Masami Hiramatsu
2015-07-21 14:17 ` Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 09/22] tracing: Add hist trigger support for multiple values ('vals=' param) Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 10/22] tracing: Add hist trigger support for compound keys Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 11/22] tracing: Add hist trigger support for user-defined sorting ('sort=' param) Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 12/22] tracing: Add hist trigger support for pausing and continuing a trace Tom Zanussi
2015-07-22 8:20 ` Masami Hiramatsu
2015-07-22 20:22 ` Tom Zanussi
2015-07-23 14:06 ` Masami Hiramatsu
2015-07-23 15:58 ` Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 13/22] tracing: Add hist trigger support for clearing " Tom Zanussi
2015-07-22 13:50 ` Masami Hiramatsu
2015-07-22 20:24 ` Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 14/22] tracing: Add hist trigger 'hex' modifier for displaying numeric fields Tom Zanussi
2015-07-19 13:22 ` Namhyung Kim [this message]
2015-07-21 14:10 ` Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 15/22] tracing: Add hist trigger 'sym' and 'sym-offset' modifiers Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 16/22] tracing: Add hist trigger 'execname' modifier Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 17/22] tracing: Add hist trigger 'syscall' modifier Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 18/22] tracing: Add hist trigger support for stacktraces as keys Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 19/22] tracing: Support string type key properly Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 20/22] tracing: Remove restriction on string position in hist trigger keys Tom Zanussi
2015-07-19 13:31 ` Namhyung Kim
2015-07-21 14:15 ` Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 21/22] tracing: Add enable_hist/disable_hist triggers Tom Zanussi
2015-07-20 14:57 ` Masami Hiramatsu
2015-07-21 16:10 ` Tom Zanussi
2015-07-22 14:21 ` Masami Hiramatsu
2015-07-22 20:18 ` Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 22/22] tracing: Add 'hist' trigger Documentation Tom Zanussi
2015-07-21 9:40 ` [PATCH v9 00/22] tracing: 'hist' triggers Masami Hiramatsu
2015-07-21 14:18 ` Tom Zanussi
2015-07-22 18:29 ` Brendan Gregg
2015-07-23 1:55 ` 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=20150719132233.GD25163@danjae.kornet \
--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=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
Powered by JetHome