From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Kirill Smelkov <kirr@mns.spb.ru>,
Frederic Weisbecker <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>,
Tom Zanussi <tzanussi@gmail.com>
Subject: Re: Q: perf log mode?
Date: Wed, 12 Jan 2011 14:30:22 -0200 [thread overview]
Message-ID: <20110112163022.GF11968@ghostprotocols.net> (raw)
In-Reply-To: <1294844553.19601.53.camel@laptop>
Em Wed, Jan 12, 2011 at 04:02:33PM +0100, Peter Zijlstra escreveu:
> On Wed, 2011-01-12 at 17:59 +0300, Kirill Smelkov wrote:
> >
> > Anyway, maybe something like this could be useful?
> >
> I guess that would be ok, but I'll leave that to Arnaldo.
It is OK, I'll apply it to my perf/core, for the next merge window.
> Also note that Arnaldo is revamping the whole script interface to make
> it possible to open and use the perf fds from the script language itself
> (the only sane way), completely removing the dependency on perf-record.
Yep, I'm librarising the ad-hoc counter creation routines we have in
stat, top and record, factoring the common parts, etc, and creating
'perf test' regression test routines for these new library functions.
After I finish the mmap bits, which should be soon, I'll start work on
having a python binding for these routines and experiment plugging it to
some other projects I worked on.
I'll also work on converting a few of the scripts we have to provide
examples of use of this python binding.
Other bindings and a C library can come later, after we settle on an API
using the python binding as the guinea pig.
Parts of this got into this merge window, for instance, perf stat uses
the perf_evsel api to open and read counters, and perf test has new
routines to stress them, new stuff I'm stashing at the perf/test branch
in:
http://git.kernel.org/?p=linux/kernel/git/acme/linux-2.6.git;a=shortlog;h=refs/heads/perf/test
- Arnaldo
next prev parent reply other threads:[~2011-01-12 16:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 14:06 Q: perf log mode? Kirill Smelkov
2011-01-12 14:08 ` Peter Zijlstra
2011-01-12 14:42 ` Frederic Weisbecker
2011-01-12 14:53 ` Peter Zijlstra
2011-01-12 15:10 ` Frederic Weisbecker
2011-01-12 14:59 ` Kirill Smelkov
2011-01-12 15:02 ` Peter Zijlstra
2011-01-12 16:30 ` Arnaldo Carvalho de Melo [this message]
2011-01-13 8:26 ` Kirill Smelkov
2011-01-12 15:21 ` Arnaldo Carvalho de Melo
2011-01-12 16:31 ` Kirill Smelkov
2011-01-12 17:07 ` Arnaldo Carvalho de Melo
2011-01-14 7:25 ` [tip:perf/urgent] perf record: Add "nodelay" mode, disabled by default tip-bot for Kirill Smelkov
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=20110112163022.GF11968@ghostprotocols.net \
--to=acme@infradead.org \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=kirr@mns.spb.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--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