public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Pierre Tardy <tardyp@gmail.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Tom Zanussi <tzanussi@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] trace-event-python: give field dict to unhandled callback
Date: Mon, 31 May 2010 23:23:15 +0200	[thread overview]
Message-ID: <20100531212312.GG5157@nowhere> (raw)
In-Reply-To: <1275340329-2397-1-git-send-email-tardyp@gmail.com>

On Mon, May 31, 2010 at 11:12:09PM +0200, Pierre Tardy wrote:
> trace_unhandled() callback does not allow to access event fields, this
> patch resolves the problem.
> 
> It can also been used as a more pythonic and flexible way for script
> writters to demux event types
> 
> This will for example greatly simplify pytimechart event demux.
> 
> Signed-off-by: Pierre Tardy <tardyp@gmail.com>
> ---
>  tools/perf/scripts/python/check-perf-trace.py      |    3 +-
>  .../util/scripting-engines/trace-event-python.c    |   50 +++++++++++++------
>  2 files changed, 35 insertions(+), 18 deletions(-)
> 
> diff --git a/tools/perf/scripts/python/check-perf-trace.py b/tools/perf/scripts/python/check-perf-trace.py
> index 964d934..d9f7893 100644
> --- a/tools/perf/scripts/python/check-perf-trace.py
> +++ b/tools/perf/scripts/python/check-perf-trace.py
> @@ -51,8 +51,7 @@ def kmem__kmalloc(event_name, context, common_cpu,
>  
>  		flag_str("kmem__kmalloc", "gfp_flags", gfp_flags)),
>  
> -def trace_unhandled(event_name, context, common_cpu, common_secs, common_nsecs,
> -		common_pid, common_comm):
> +def trace_unhandled(event_name, context, event_fields_dict):
>      try:
>          unhandled[event_name] += 1
>      except TypeError:
> diff --git a/tools/perf/util/scripting-engines/trace-event-python.c b/tools/perf/util/scripting-engines/trace-event-python.c
> index 81f39ca..33a6325 100644
> --- a/tools/perf/util/scripting-engines/trace-event-python.c
> +++ b/tools/perf/util/scripting-engines/trace-event-python.c
> @@ -208,7 +208,7 @@ static void python_process_event(int cpu, void *data,
>  				 int size __unused,
>  				 unsigned long long nsecs, char *comm)
>  {
> -	PyObject *handler, *retval, *context, *t, *obj;
> +	PyObject *handler, *retval, *context, *t, *obj, *dict = NULL;
>  	static char handler_name[256];
>  	struct format_field *field;
>  	unsigned long long val;
> @@ -232,6 +232,14 @@ static void python_process_event(int cpu, void *data,
>  
>  	sprintf(handler_name, "%s__%s", event->system, event->name);
>  
> +	handler = PyDict_GetItemString(main_dict, handler_name);
> +	if (handler && !PyCallable_Check(handler))
> +		handler = NULL;
> +	if (!handler) {
> +		dict = PyDict_New();
> +		if (!dict)
> +			Py_FatalError("couldn't create Python dict");
> +	}
>  	s = nsecs / NSECS_PER_SEC;
>  	ns = nsecs - s * NSECS_PER_SEC;
>  
> @@ -242,12 +250,20 @@ static void python_process_event(int cpu, void *data,
>  	PyTuple_SetItem(t, n++, PyString_FromString(handler_name));
>  	PyTuple_SetItem(t, n++,
>  			PyCObject_FromVoidPtr(scripting_context, NULL));
> -	PyTuple_SetItem(t, n++, PyInt_FromLong(cpu));
> -	PyTuple_SetItem(t, n++, PyInt_FromLong(s));
> -	PyTuple_SetItem(t, n++, PyInt_FromLong(ns));
> -	PyTuple_SetItem(t, n++, PyInt_FromLong(pid));
> -	PyTuple_SetItem(t, n++, PyString_FromString(comm));
>  
> +	if (handler) {
> +		PyTuple_SetItem(t, n++, PyInt_FromLong(cpu));
> +		PyTuple_SetItem(t, n++, PyInt_FromLong(s));
> +		PyTuple_SetItem(t, n++, PyInt_FromLong(ns));
> +		PyTuple_SetItem(t, n++, PyInt_FromLong(pid));
> +		PyTuple_SetItem(t, n++, PyString_FromString(comm));
> +	} else {
> +		PyDict_SetItemString(dict, "common_cpu", PyInt_FromLong(cpu));
> +		PyDict_SetItemString(dict, "common_s", PyInt_FromLong(s));
> +		PyDict_SetItemString(dict, "common_ns", PyInt_FromLong(ns));
> +		PyDict_SetItemString(dict, "common_pid", PyInt_FromLong(pid));
> +		PyDict_SetItemString(dict, "common_comm", PyString_FromString(comm));
> +	}
>  	for (field = event->format.fields; field; field = field->next) {
>  		if (field->flags & FIELD_IS_STRING) {
>  			int offset;
> @@ -272,27 +288,31 @@ static void python_process_event(int cpu, void *data,
>  					obj = PyLong_FromUnsignedLongLong(val);
>  			}
>  		}
> -		PyTuple_SetItem(t, n++, obj);
> +		if (handler)
> +			PyTuple_SetItem(t, n++, obj);
> +		else
> +			PyDict_SetItemString(dict, field->name, obj);
> +
>  	}
> +	if (!handler)
> +		PyTuple_SetItem(t, n++, dict);
>  
>  	if (_PyTuple_Resize(&t, n) == -1)
>  		Py_FatalError("error resizing Python tuple");
>  
> -	handler = PyDict_GetItemString(main_dict, handler_name);
> -	if (handler && PyCallable_Check(handler)) {
> +	if (handler) {
>  		retval = PyObject_CallObject(handler, t);
>  		if (retval == NULL)
>  			handler_call_die(handler_name);
>  	} else {
>  		handler = PyDict_GetItemString(main_dict, "trace_unhandled");
>  		if (handler && PyCallable_Check(handler)) {
> -			if (_PyTuple_Resize(&t, N_COMMON_FIELDS) == -1)
> -				Py_FatalError("error resizing Python tuple");
>  
>  			retval = PyObject_CallObject(handler, t);
>  			if (retval == NULL)
>  				handler_call_die("trace_unhandled");
>  		}
> +		Py_DECREF(dict);



Cool!

Acked-by: Frederic Weisbecker <fweisbec@gmail.com>


  reply	other threads:[~2010-05-31 21:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-29 15:42 [PATCH] trace-event-python: give field dict to unhandled callback Pierre Tardy
2010-05-31 16:23 ` Pierre Tardy
2010-05-31 19:06   ` Tom Zanussi
2010-05-31 21:07     ` Pierre Tardy
2010-05-31 21:12       ` Pierre Tardy
2010-05-31 21:23         ` Frederic Weisbecker [this message]
2010-05-31 21:36         ` Tom Zanussi
2010-06-02  7:43         ` [tip:perf/urgent] perf scripts python: Give " tip-bot for Pierre Tardy

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=20100531212312.GG5157@nowhere \
    --to=fweisbec@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tardyp@gmail.com \
    --cc=tzanussi@gmail.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