public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 24/37] tracing: Add support for 'synthetic' events
Date: Tue, 14 Nov 2017 19:06:47 +0900	[thread overview]
Message-ID: <20171114100647.GA20669@sejong> (raw)
In-Reply-To: <f97c1be3678794dad81ea1d523ca6da3f088e646.1510252666.git.tom.zanussi@linux.intel.com>

On Thu, Nov 09, 2017 at 02:33:55PM -0600, Tom Zanussi wrote:
> Synthetic events are user-defined events generated from hist trigger
> variables saved from one or more other events.
> 
> To define a synthetic event, the user writes a simple specification
> consisting of the name of the new event along with one or more
> variables and their type(s), to the tracing/synthetic_events file.
> 
> For instance, the following creates a new event named 'wakeup_latency'
> with 3 fields: lat, pid, and prio:
> 
>     # echo 'wakeup_latency u64 lat; pid_t pid; int prio' >> \
>       /sys/kernel/debug/tracing/synthetic_events
> 
> Reading the tracing/synthetic_events file lists all the
> currently-defined synthetic events, in this case the event we defined
> above:
> 
>     # cat /sys/kernel/debug/tracing/synthetic_events
>     wakeup_latency u64 lat; pid_t pid; int prio
> 
> At this point, the synthetic event is ready to use, and a histogram
> can be defined using it:
> 
>     # echo 'hist:keys=pid,prio,lat.log2:sort=pid,lat' >> \
>     /sys/kernel/debug/tracing/events/synthetic/wakeup_latency/trigger
> 
> The new event is created under the tracing/events/synthetic/ directory
> and looks and behaves just like any other event:
> 
>     # ls /sys/kernel/debug/tracing/events/synthetic/wakeup_latency
>       enable  filter  format  hist  id  trigger
> 
> Although a histogram can be defined for it, nothing will happen until
> an action tracing that event via the trace_synth() function occurs.
> The trace_synth() function is very similar to all the other trace_*
> invocations spread throughout the kernel, except in this case the
> trace_ function and its corresponding tracepoint isn't statically
> generated but defined by the user at run-time.
> 
> How this can be automatically hooked up via a hist trigger 'action' is
> discussed in a subsequent patch.
> 
> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
> ---
>  kernel/trace/trace_events_hist.c | 908 ++++++++++++++++++++++++++++++++++++++-
>  1 file changed, 906 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/trace/trace_events_hist.c b/kernel/trace/trace_events_hist.c
> index 3504aa8..510b10d 100644
> --- a/kernel/trace/trace_events_hist.c
> +++ b/kernel/trace/trace_events_hist.c
> @@ -20,10 +20,16 @@
>  #include <linux/slab.h>
>  #include <linux/stacktrace.h>
>  #include <linux/rculist.h>
> +#include <linux/tracefs.h>
>  
>  #include "tracing_map.h"
>  #include "trace.h"
>  
> +#define SYNTH_SYSTEM		"synthetic"
> +#define SYNTH_FIELDS_MAX	16
> +
> +#define STR_VAR_LEN_MAX		32 /* must be multiple of sizeof(u64) */
> +
>  struct hist_field;
>  
>  typedef u64 (*hist_field_fn_t) (struct hist_field *field,
> @@ -270,6 +276,26 @@ struct hist_trigger_data {
>  	unsigned int			n_actions;
>  };
>  
> +struct synth_field {
> +	char *type;
> +	char *name;
> +	size_t size;
> +	bool is_signed;
> +	bool is_string;
> +};
> +
> +struct synth_event {
> +	struct list_head			list;
> +	int					ref;
> +	char					*name;
> +	struct synth_field			**fields;
> +	unsigned int				n_fields;
> +	unsigned int				n_u64;
> +	struct trace_event_class		class;
> +	struct trace_event_call			call;
> +	struct tracepoint			*tp;
> +};
> +
>  struct action_data;
>  
>  typedef void (*action_fn_t) (struct hist_trigger_data *hist_data,
> @@ -282,6 +308,803 @@ struct action_data {
>  	unsigned int		var_ref_idx;
>  };
>  
> +static LIST_HEAD(synth_event_list);
> +static DEFINE_MUTEX(synth_event_mutex);
> +
> +struct synth_trace_event {
> +	struct trace_entry	ent;
> +	u64			fields[];
> +};
> +
> +static int synth_event_define_fields(struct trace_event_call *call)
> +{
> +	struct synth_trace_event trace;
> +	int offset = offsetof(typeof(trace), fields);
> +	struct synth_event *event = call->data;
> +	unsigned int i, size, n_u64;
> +	char *name, *type;
> +	bool is_signed;
> +	int ret = 0;
> +
> +	for (i = 0, n_u64 = 0; i < event->n_fields; i++) {
> +		size = event->fields[i]->size;
> +		is_signed = event->fields[i]->is_signed;
> +		type = event->fields[i]->type;
> +		name = event->fields[i]->name;
> +		ret = trace_define_field(call, type, name, offset, size,
> +					 is_signed, FILTER_OTHER);
> +		if (ret)
> +			break;
> +
> +		if (event->fields[i]->is_string) {
> +			offset += STR_VAR_LEN_MAX;
> +			n_u64 += STR_VAR_LEN_MAX / sizeof(u64);

Did you use fixed size array for strings?


> +		} else {
> +			offset += sizeof(u64);
> +			n_u64++;
> +		}
> +	}
> +
> +	event->n_u64 = n_u64;
> +
> +	return ret;
> +}
> +
> +static bool synth_field_signed(char *type)
> +{
> +	if (strncmp(type, "u", 1) == 0)
> +		return false;
> +
> +	return true;
> +}
> +
> +static int synth_field_is_string(char *type)
> +{
> +	if (strstr(type, "char[") != NULL)
> +		return true;
> +
> +	return false;
> +}
> +
> +static int synth_field_string_size(char *type)
> +{
> +	char buf[4], *end, *start;
> +	unsigned int len;
> +	int size, err;
> +
> +	start = strstr(type, "char[");
> +	if (start == NULL)
> +		return -EINVAL;
> +	start += strlen("char[");
> +
> +	end = strchr(type, ']');
> +	if (!end || end < start)
> +		return -EINVAL;
> +
> +	len = end - start;
> +	if (len > 3)
> +		return -EINVAL;
> +
> +	strncpy(buf, start, len);
> +	buf[len] = '\0';
> +
> +	err = kstrtouint(buf, 0, &size);
> +	if (err)
> +		return err;
> +
> +	if (size > STR_VAR_LEN_MAX)
> +		return -EINVAL;
> +
> +	return size;
> +}

But this seems to use the actual array size for string..

[SNIP]
> +
> +static notrace void trace_event_raw_event_synth(void *__data,
> +						u64 *var_ref_vals,
> +						unsigned int var_ref_idx)
> +{
> +	struct trace_event_file *trace_file = __data;
> +	struct synth_trace_event *entry;
> +	struct trace_event_buffer fbuffer;
> +	struct synth_event *event;
> +	unsigned int i, n_u64;
> +	int fields_size = 0;
> +
> +	event = trace_file->event_call->data;
> +
> +	if (trace_trigger_soft_disabled(trace_file))
> +		return;
> +
> +	fields_size = event->n_u64 * sizeof(u64);
> +
> +	entry = trace_event_buffer_reserve(&fbuffer, trace_file,
> +					   sizeof(*entry) + fields_size);
> +	if (!entry)
> +		return;
> +
> +	for (i = 0, n_u64 = 0; i < event->n_fields; i++) {
> +		if (event->fields[i]->is_string) {
> +			char *str_val = (char *)(long)var_ref_vals[var_ref_idx + i];
> +			char *str_field = (char *)&entry->fields[n_u64];
> +
> +			strncpy(str_field, str_val, STR_VAR_LEN_MAX);
> +			n_u64 += STR_VAR_LEN_MAX / sizeof(u64);

Here it uses the fixed size again..

Thanks,
Namhyung


> +		} else {
> +			entry->fields[i] = var_ref_vals[var_ref_idx + i];
> +			n_u64++;
> +		}
> +	}
> +
> +	trace_event_buffer_commit(&fbuffer);
> +}

  parent reply	other threads:[~2017-11-14 10:06 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
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 [this message]
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=20171114100647.GA20669@sejong \
    --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