public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Feng Tang <feng.tang@intel.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] perf, x86: Enabled PEBS event to be exported in a raw format
Date: Thu, 28 Jun 2012 11:26:49 -0700	[thread overview]
Message-ID: <20120628182649.GS4152@tassilo.jf.intel.com> (raw)
In-Reply-To: <CABPqkBQ6Ot8fQLtMCbAiPFWPhajaGB-HEsYmLYRY8_Xee8sBNg@mail.gmail.com>

> My problem with the script approach is that you may end up
> re-inventing a lot of the infrastructure
> already in perf in terms of histograming and sorting. I think scripts

All built into modern scripting languages. Only in C you have to reinvent
it.

> are good for dumping
> the raw data or very simply analysis. Now I recognize that they are
> handy to implement
> mahcine specific decoding of the samples.

The main use case is really custom analysis, so that people can do
whatever custom data mining they want.

But I expect once you get users engaged with a simple interface
you'll get much more. 

But even the existing script is quite useful and gives you
a lot of information. It's also very easy to extend to everyone
knowing SQLite.

Can you do all these things the simple script does?

-Andi

  parent reply	other threads:[~2012-06-28 18:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 16:00 [PATCH] perf, x86: Enabled PEBS event to be exported in a raw format Feng Tang
2012-06-28 16:12 ` Peter Zijlstra
2012-06-28 16:15   ` Stephane Eranian
2012-06-28 16:19     ` Peter Zijlstra
2012-06-28 16:27       ` Stephane Eranian
2012-06-28 16:29         ` Peter Zijlstra
2012-06-28 18:26         ` Andi Kleen [this message]
2012-06-28 18:20   ` Andi Kleen
2012-06-28 20:51     ` Peter Zijlstra
2012-06-29  1:32       ` Feng Tang
2012-06-29  3:35         ` Andi Kleen
2012-06-29 12:49     ` Ingo Molnar
2012-07-03  7:36 ` Michael Ellerman
2012-07-03  9:15   ` Peter Zijlstra
2012-07-04  8:07     ` Michael Ellerman
2012-07-04  9:13       ` Peter Zijlstra
2012-07-05 15:57         ` Stephane Eranian
2012-07-07  7:27           ` Michael Ellerman

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=20120628182649.GS4152@tassilo.jf.intel.com \
    --to=ak@linux.intel.com \
    --cc=acme@redhat.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=x86@kernel.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