From: Andi Kleen <andi@firstfloor.org>
To: Adrien BAK <adrien.bak@numscale.com>
Cc: a.p.zijlstra@chello.nl, paulus@samba.org, mingo@redhat.com,
acme@kernel.org, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf tools : adds support for native scripting
Date: Thu, 22 May 2014 04:24:11 -0700 [thread overview]
Message-ID: <871tvmqco4.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <1400727182.19852.0.camel@desktop> (Adrien BAK's message of "Thu, 22 May 2014 11:53:02 +0900")
Adrien BAK <adrien.bak@numscale.com> writes:
> As it is perf-script allows one to use perl or python scripts to parse
> perf events.
> The following proposal aimed to introduce support of .so files as scripts.
> This support allows for better performance when parsing perf's data
> files and a complete access to the raw data.
You'll at least need some documentation how to use it.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2014-05-22 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 2:53 [PATCH] perf tools : adds support for native scripting Adrien BAK
2014-05-22 11:24 ` Andi Kleen [this message]
2014-09-06 15:06 ` Milian Wolff
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=871tvmqco4.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=adrien.bak@numscale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
/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