linux-rt-users.vger.kernel.org archive mirror
 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, fengguang.wu@intel.com,
	linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
	kernel-team@lge.com
Subject: Re: [PATCH v8 24/37] tracing: Add support for 'synthetic' events
Date: Wed, 10 Jan 2018 14:41:24 +0900	[thread overview]
Message-ID: <20180110054124.GA2575@danjae.aot.lge.com> (raw)
In-Reply-To: <c8c526d55c308b108d1a1129cdd44af988581937.1513802700.git.tom.zanussi@linux.intel.com>

Hi Tom,

On Thu, Dec 21, 2017 at 10:02:46AM -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>
> [fix noderef.cocci warnings, sizeof pointer for kcalloc of event->fields]
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> ---

[SNIP]
> +static int release_all_synth_events(void)
> +{
> +	struct list_head release_events;
> +	struct synth_event *event, *e;
> +	int ret = 0, err = 0;
> +
> +	INIT_LIST_HEAD(&release_events);
> +
> +	mutex_lock(&synth_event_mutex);
> +
> +	list_for_each_entry(event, &synth_event_list, list) {
> +		if (event->ref) {
> +			mutex_unlock(&synth_event_mutex);
> +			return -EBUSY;
> +		}
> +	}
> +
> +	list_for_each_entry_safe(event, e, &synth_event_list, list)
> +		list_move(&event->list, &release_events);

list_splice_init() ?

> +
> +	mutex_unlock(&synth_event_mutex);
> +
> +	list_for_each_entry_safe(event, e, &release_events, list) {
> +		list_del(&event->list);
> +
> +		ret = unregister_synth_event(event);
> +		add_or_delete_synth_event(event, !ret);
> +	}
> +
> +	if (err)
> +		ret = err;

The err was never used.

> +
> +	return ret;
> +}

  reply	other threads:[~2018-01-10  5:41 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21 16:02 [PATCH v8 00/37] tracing: Inter-event (e.g. latency) support Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 01/37] tracing: Move hist trigger Documentation to histogram.txt Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 02/37] tracing: Add Documentation for log2 modifier Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 03/37] tracing: Add support to detect and avoid duplicates Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 04/37] tracing: Remove code which merges duplicates Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 05/37] ring-buffer: Add interface for setting absolute time stamps Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 06/37] ring-buffer: Redefine the unimplemented RINGBUF_TYPE_TIME_STAMP Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 07/37] tracing: Add timestamp_mode trace file Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 08/37] tracing: Give event triggers access to ring_buffer_event Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 09/37] tracing: Add ring buffer event param to hist field functions Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 10/37] tracing: Break out hist trigger assignment parsing Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 11/37] tracing: Add hist trigger timestamp support Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 12/37] tracing: Add per-element variable support to tracing_map Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 13/37] tracing: Add hist_data member to hist_field Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 14/37] tracing: Add usecs modifier for hist trigger timestamps Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 15/37] tracing: Add variable support to hist triggers Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 16/37] tracing: Account for variables in named trigger compatibility Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 17/37] tracing: Move get_hist_field_flags() Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 18/37] tracing: Add simple expression support to hist triggers Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 19/37] tracing: Generalize per-element hist trigger data Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 20/37] tracing: Pass tracing_map_elt to hist_field accessor functions Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 21/37] tracing: Add hist_field 'type' field Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 22/37] tracing: Add variable reference handling to hist triggers Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 23/37] tracing: Add hist trigger action hook Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 24/37] tracing: Add support for 'synthetic' events Tom Zanussi
2018-01-10  5:41   ` Namhyung Kim [this message]
2017-12-21 16:02 ` [PATCH v8 25/37] tracing: Add support for 'field variables' Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 26/37] tracing: Add 'onmatch' hist trigger action support Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 27/37] tracing: Add 'onmax' " Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 28/37] tracing: Allow whitespace to surround hist trigger filter Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 29/37] tracing: Add cpu field for hist triggers Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 30/37] tracing: Add hist trigger support for variable reference aliases Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 31/37] tracing: Add 'last error' error facility for hist triggers Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 32/37] tracing: Add inter-event hist trigger Documentation Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 33/37] tracing: Make tracing_set_clock() non-static Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 34/37] tracing: Add a clock attribute for hist triggers Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 35/37] tracing: Increase trace_recursive_lock() limit for synthetic events Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 36/37] tracing: Add inter-event blurb to HIST_TRIGGERS config option Tom Zanussi
2017-12-21 16:02 ` [PATCH v8 37/37] selftests: ftrace: Add inter-event hist triggers testcases Tom Zanussi
2018-01-10  5:45 ` [PATCH v8 00/37] tracing: Inter-event (e.g. latency) support Namhyung Kim
2018-01-10  7:20   ` Steven Rostedt
2018-01-10  8:16     ` Namhyung Kim
2018-01-10 15:18       ` Tom Zanussi
2018-01-15 22:43         ` Steven Rostedt
2018-01-16  2:43           ` 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=20180110054124.GA2575@danjae.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=baohong.liu@intel.com \
    --cc=bigeasy@linutronix.de \
    --cc=fengguang.wu@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).