mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Feng Tang <feng.tang@intel.com>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: <mingo@elte.hu>, <a.p.zijlstra@chello.nl>,
	<robert.richter@amd.com>, <ak@linux.intel.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] perf script/python: Pass thread/dso name and symbol info to event handler in python
Date: Sat, 19 May 2012 22:13:30 +0800	[thread overview]
Message-ID: <20120519221330.08b24ed1@feng-i7> (raw)
In-Reply-To: <20120518153854.GF2636@infradead.org>

Hi Arnaldo,


On Fri, 18 May 2012 12:38:54 -0300
Arnaldo Carvalho de Melo <acme@redhat.com> wrote:

> Em Fri, May 18, 2012 at 10:55:27AM +0800, Feng Tang escreveu:
> > On Thu, 17 May 2012 12:47:26 -0300
> > Arnaldo Carvalho de Melo <acme@redhat.com> wrote:
> > > >  	PyTuple_SetItem(t, n++, PyString_FromStringAndSize(
> > > >  			data, sample->raw_size));
> > > > +	PyTuple_SetItem(t, n++, PyString_FromString(thread->comm));
> > > > +	PyTuple_SetItem(t, n++,
> > > > PyString_FromString(al->map->dso->name)); +
> > > > +	/* Pass the resolved symbol if there is, othersize pass
> > > > "Unkown" */
> > > > +	if (al->sym)
> > > > +		PyTuple_SetItem(t, n++,
> > > > PyString_FromString(al->sym->name));
> > > > +	else
> > > > +		PyTuple_SetItem(t, n++,
> > > > PyString_FromString("Unknown"));
> > > 
> > > Isn't this getting a little bit convoluted?
> > > 
> > > I.e. python has dictionaries, perhaps we could pass a dict instead of a
> > > tuple, in that case we would simply not add the "symbol" key.
> > 
> > IIRC, the PyObject_CallObjects() only accept "tuple" arguments, or did
> > you mean make the "symbol" a dict and an item of the "t" tuple?
> > 
> > I agree the symbol code is ugly, is following a little better?	
> > 	PyTuple_SetItem(t, n++, PyString_FromString((al->sym) ?
> > al->sym->name : "Unknown"));
> 
> What I meant was: make it so that the process_event() python method we
> look for receives as its first argument a dict.
> 
> I.e. pass a tuple to PyObject_CallObjects() that has just one entry: a
> dict.
> 
> This way if we need to add more parameters in the future, some of which
> may not exist (the "Unknown" ones). This way older scripts will continue
> working with newer perf tools, they just won't process the new stuff.

Got your point now. I've modified the code as you suggested and tested
them with my script which worked fine. Will send out a V2 for the whole
patch set after I got comments from David Ahern for my [PATCH 2/3]. Thanks,

- Feng

> 
> I.e. when adding features make sure that old scripts works with newer
> perf tools and vice versa as much as possible. If not possible, add
> notes to the relevant tools/perf/Documentation/ file.
> 
> - Arnaldo

  reply	other threads:[~2012-05-19 14:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 12:59 [PATCH 1/3] perf script: Add general python handler to process non-tracepoint events Feng Tang
2012-05-16 12:59 ` [PATCH 2/3] perf script: Replace "struct thread" with "struct addr_location" as a parameter for "process_event()" Feng Tang
2012-05-17 15:45   ` Arnaldo Carvalho de Melo
2012-05-17 16:08     ` David Ahern
2012-05-17 16:22       ` Arnaldo Carvalho de Melo
2012-05-30 16:10     ` David Ahern
2012-05-16 12:59 ` [PATCH 3/3] perf script/python: Pass thread/dso name and symbol info to event handler in python Feng Tang
2012-05-17 15:47   ` Arnaldo Carvalho de Melo
2012-05-18  2:55     ` Feng Tang
2012-05-18 15:38       ` Arnaldo Carvalho de Melo
2012-05-19 14:13         ` Feng Tang [this message]
2012-05-17 15:43 ` [PATCH 1/3] perf script: Add general python handler to process non-tracepoint events Arnaldo Carvalho de Melo
2012-05-18  2:48   ` Feng Tang
2012-05-18 15:34     ` Arnaldo Carvalho de Melo

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=20120519221330.08b24ed1@feng-i7 \
    --to=feng.tang@intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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