linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Stephane Eranian <eranian@google.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Jiri Olsa <jolsa@redhat.com>, Mike Galbraith <efault@gmx.de>,
	Namhyung Kim <namhyung@gmail.com>,
	Paul Mackerras <paulus@samba.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 12/15] perf tools: allow non-matching sample types
Date: Wed, 26 Jun 2013 15:00:59 -0600	[thread overview]
Message-ID: <51CB568B.4030605@gmail.com> (raw)
In-Reply-To: <CABPqkBR=5TxFX=3J=p7EAPcbwK7E93rM1X4GKGsuw0Eopcf+6Q@mail.gmail.com>

On 6/26/13 2:54 PM, Stephane Eranian wrote:
> On Wed, Jun 26, 2013 at 10:48 PM, David Ahern <dsahern@gmail.com> wrote:
>> Arnaldo:
>>
>> I noticed this patch in your perf/core branch. I do not think this one is
>> ready to be committed. It does not fully solve the problem of allowing
>> non-matching sample types.
>>
>> I have a set of patches here on github that work fine for one use case --
>> mixed s/w and tracepoint events:
>> https://github.com/dsahern/linux/tree/multiple-sample_type
>>
>> I'll push the patches out, but wanted to run some more test cases first.
>>
> All those solutions address the need of perf but they do not fix the fundamental
> problem that the kernel is exporting a un-parseable file in case of different
> sample_type for each event. We need to fix the generic case so that other
> tools don't have to deal with this. I will post a patch which can solve this
> in the kernel and yet remain backward compatible. But I don't  have the
> perf portion of the patch, hoping somebody can help with developing it.

The patchset in the URL above attempts to find the id which correlates 
to the evsel which has the sample_type. It starts at the max index (IP, 
TID, TIME and ADDR all requested which means an index of 4 for the ID) 
and then works its way in (meaning one of the above is not requested).

Would be better for the event sample to put the id at the front or the 
sample_type at the front, but that ship has sailed. It would be nice to 
have a userspace option that works with existing kernels.

I'll take a look at your kernel change when you post it to see what I am 
overlooking here but the patches have worked fine for me so far.

David


  reply	other threads:[~2013-06-26 21:01 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 13:15 [PATCH 00/15] perf tools: some fixes and tweaks Adrian Hunter
2013-06-24 13:15 ` [PATCH 01/15] perf tools: remove unused parameter Adrian Hunter
2013-06-25 13:58   ` Jiri Olsa
2013-06-24 13:15 ` [PATCH 02/15] perf tools: fix missing tool parameter Adrian Hunter
2013-06-25 13:04   ` Jiri Olsa
2013-06-27  7:58     ` Adrian Hunter
2013-06-24 13:16 ` [PATCH 03/15] perf tools: fix missing 'finished_round' Adrian Hunter
2013-06-25 13:58   ` Jiri Olsa
2013-06-24 13:16 ` [PATCH 04/15] perf tools: fix parse_events_terms() segfault on error path Adrian Hunter
2013-06-25 13:59   ` Jiri Olsa
2013-06-24 13:16 ` [PATCH 05/15] perf tools: fix new_term() missing free " Adrian Hunter
2013-06-25 13:59   ` Jiri Olsa
2013-06-24 13:16 ` [PATCH 06/15] perf tools: fix parse_events_terms() freeing local variable " Adrian Hunter
2013-06-25 13:13   ` Jiri Olsa
2013-06-27  7:59     ` Adrian Hunter
2013-06-24 13:16 ` [PATCH 07/15] perf tools: add const specifier to perf_pmu__find name parameter Adrian Hunter
2013-06-24 13:16 ` [PATCH 08/15] perf tools: tidy duplicated munmap code Adrian Hunter
2013-06-25 14:00   ` Jiri Olsa
2013-06-24 13:16 ` [PATCH 09/15] perf tools: validate perf event header size Adrian Hunter
2013-06-25 13:18   ` Jiri Olsa
2013-06-27  7:59     ` Adrian Hunter
2013-06-26  1:44   ` Namhyung Kim
2013-06-27  8:01     ` Adrian Hunter
2013-06-24 13:16 ` [PATCH 10/15] perf tools: add debug prints Adrian Hunter
2013-06-25 14:01   ` Jiri Olsa
2013-06-24 13:16 ` [PATCH 11/15] perf tools: fix symbol_conf.nr_events Adrian Hunter
2013-06-24 13:16 ` [PATCH 12/15] perf tools: allow non-matching sample types Adrian Hunter
2013-06-25 11:23   ` Stephane Eranian
2013-06-25 12:13     ` Adrian Hunter
2013-06-25 14:45       ` Jiri Olsa
2013-06-25 15:42         ` David Ahern
2013-06-25 16:04           ` Jiri Olsa
2013-06-25 12:32   ` Jiri Olsa
2013-06-27  7:57     ` Adrian Hunter
2013-06-25 15:56   ` David Ahern
2013-06-25 16:03     ` Stephane Eranian
2013-06-25 23:04       ` David Ahern
2013-06-25 23:27         ` David Ahern
2013-06-27  8:02     ` Adrian Hunter
2013-06-26 20:48   ` David Ahern
2013-06-26 20:54     ` Stephane Eranian
2013-06-26 21:00       ` David Ahern [this message]
2013-06-26 21:07         ` Stephane Eranian
2013-06-24 13:16 ` [PATCH 13/15] perf tools: struct thread has a tid not a pid Adrian Hunter
2013-06-24 13:16 ` [PATCH 14/15] perf tools: add pid to struct thread Adrian Hunter
2013-06-24 13:16 ` [PATCH 15/15] perf tools: fix ppid in thread__fork() Adrian Hunter
2013-06-25 16:00   ` David Ahern
2013-06-25 16:04     ` David Ahern

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=51CB568B.4030605@gmail.com \
    --to=dsahern@gmail.com \
    --cc=acme@ghostprotocols.net \
    --cc=adrian.hunter@intel.com \
    --cc=efault@gmx.de \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@gmail.com \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).