lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 18 May 2012 12:38:54 -0300
From:	Arnaldo Carvalho de Melo <acme@...hat.com>
To:	Feng Tang <feng.tang@...el.com>
Cc:	mingo@...e.hu, a.p.zijlstra@...llo.nl, robert.richter@....com,
	ak@...ux.intel.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] perf script/python: Pass thread/dso name and symbol
 info to event handler in python

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@...hat.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.

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ