From: Namhyung Kim <namhyung@kernel.org>
To: Feng Tang <feng.tang@intel.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
David Ahern <dsahern@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Robert Richter <robert.richter@amd.com>,
Andi Kleen <andi@firstfloor.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH v5 3/5] perf script/python: Pass event/thread/dso name and symbol info to event handler in python
Date: Thu, 09 Aug 2012 10:06:02 +0900 [thread overview]
Message-ID: <87r4rgyiv9.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1344419875-21665-4-git-send-email-feng.tang@intel.com> (Feng Tang's message of "Wed, 8 Aug 2012 17:57:53 +0800")
On Wed, 8 Aug 2012 17:57:53 +0800, Feng Tang wrote:
> Also as suggested by Arnaldo, pack all these parameters to a dictionary,
> which is more expandable for adding new parameters while keeping the
> compatibility for old scripts.
>
Just minor nits.
> Signed-off-by: Feng Tang <feng.tang@intel.com>
> Cc: David Ahern <dsahern@gmail.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Robert Richter <robert.richter@amd.com>
> Cc: Andi Kleen <andi@firstfloor.org>
> Cc: Stephane Eranian <eranian@google.com>
> ---
> .../util/scripting-engines/trace-event-python.c | 35 ++++++++++++++++---
> 1 files changed, 29 insertions(+), 6 deletions(-)
>
> diff --git a/tools/perf/util/scripting-engines/trace-event-python.c b/tools/perf/util/scripting-engines/trace-event-python.c
> index 24711b3..7e3f576 100644
> --- a/tools/perf/util/scripting-engines/trace-event-python.c
> +++ b/tools/perf/util/scripting-engines/trace-event-python.c
> @@ -345,15 +345,23 @@ static void python_process_general_event(union perf_event *perf_event __unused,
> struct machine *machine __unused,
> struct addr_location *al __unused)
@al is used now.
> {
> - PyObject *handler, *retval, *t;
> + PyObject *handler, *retval, *t, *dict;
> static char handler_name[64];
> unsigned n = 0;
> - void *data = sample->raw_data;
> + struct thread *thread = al->thread;
>
> + /*
> + * Use the MAX_FIELDS to make the function expandable, though
> + * currently there is only one itme for the tuple.
s/itme/item/
Thanks,
Namhyung
> + */
> t = PyTuple_New(MAX_FIELDS);
> if (!t)
> Py_FatalError("couldn't create Python tuple");
>
> + dict = PyDict_New();
> + if (!dict)
> + Py_FatalError("couldn't create Python dictionary");
> +
> snprintf(handler_name, sizeof(handler_name), "%s", "process_event");
>
> handler = PyDict_GetItemString(main_dict, handler_name);
> @@ -362,11 +370,25 @@ static void python_process_general_event(union perf_event *perf_event __unused,
> goto exit;
> }
>
> - /* Pass 4 parameters: event_attr, perf_sample, raw data, thread name */
> - PyTuple_SetItem(t, n++, PyString_FromStringAndSize((void *)&evsel->attr, sizeof(evsel->attr)));
> - PyTuple_SetItem(t, n++, PyString_FromStringAndSize((void *)sample, sizeof(*sample)));
> - PyTuple_SetItem(t, n++, PyString_FromStringAndSize(data, sample->raw_size));
> + PyDict_SetItemString(dict, "ev_name", PyString_FromString(perf_evsel__name(evsel)));
> + PyDict_SetItemString(dict, "attr", PyString_FromStringAndSize(
> + (const char *)&evsel->attr, sizeof(evsel->attr)));
> + PyDict_SetItemString(dict, "sample", PyString_FromStringAndSize(
> + (const char *)sample, sizeof(*sample)));
> + PyDict_SetItemString(dict, "raw_buf", PyString_FromStringAndSize(
> + (const char *)sample->raw_data, sample->raw_size));
> + PyDict_SetItemString(dict, "comm",
> + PyString_FromString(thread->comm));
> + if (al->map) {
> + PyDict_SetItemString(dict, "dso",
> + PyString_FromString(al->map->dso->name));
> + }
> + if (al->sym) {
> + PyDict_SetItemString(dict, "symbol",
> + PyString_FromString(al->sym->name));
> + }
>
> + PyTuple_SetItem(t, n++, dict);
> if (_PyTuple_Resize(&t, n) == -1)
> Py_FatalError("error resizing Python tuple");
>
> @@ -374,6 +396,7 @@ static void python_process_general_event(union perf_event *perf_event __unused,
> if (retval == NULL)
> handler_call_die(handler_name);
> exit:
> + Py_DECREF(dict);
> Py_DECREF(t);
> }
next prev parent reply other threads:[~2012-08-09 1:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 9:57 [PATCH v5 0/5] perf script: Add general event support to event handler of python script Feng Tang
2012-08-08 9:57 ` [PATCH v5 1/5] perf script: Add general python handler to process non-tracepoint events Feng Tang
2012-08-09 0:54 ` Namhyung Kim
2012-08-21 15:30 ` [tip:perf/core] " tip-bot for Feng Tang
2012-08-08 9:57 ` [PATCH v5 2/5] perf script: Replace "struct thread" with "struct addr_location" as a parameter for "process_event()" Feng Tang
2012-08-21 15:31 ` [tip:perf/core] perf script: Replace "struct thread" with " struct " tip-bot for Feng Tang
2012-08-08 9:57 ` [PATCH v5 3/5] perf script/python: Pass event/thread/dso name and symbol info to event handler in python Feng Tang
2012-08-09 1:06 ` Namhyung Kim [this message]
2012-08-21 15:32 ` [tip:perf/core] perf scripts python: Pass event/thread/ dso " tip-bot for Feng Tang
2012-08-08 9:57 ` [PATCH v5 4/5] perf script: Add a python library EventClass.py Feng Tang
2012-08-09 1:10 ` Namhyung Kim
2012-08-21 15:35 ` [tip:perf/core] perf scripts python: " tip-bot for Feng Tang
2012-08-08 9:57 ` [PATCH v5 5/5] perf script: Add event_analyzing_sample.py as a sample for general event handling Feng Tang
2012-08-09 1:30 ` Namhyung Kim
2012-08-09 4:30 ` Feng Tang
2012-08-09 5:19 ` Namhyung Kim
2012-08-09 5:28 ` Feng Tang
2012-08-09 5:46 ` Namhyung Kim
2012-08-21 15:36 ` [tip:perf/core] perf scripts python: Add event_analyzing_sample. py " tip-bot for Feng Tang
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=87r4rgyiv9.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=acme@redhat.com \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=robert.richter@amd.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