public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Ian Munsie <imunsie@au1.ibm.com>,
	linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 3/6] perf: Add timestamp to COMM and MMAP events
Date: Fri, 26 Nov 2010 19:54:30 -0200	[thread overview]
Message-ID: <20101126215430.GA23996@ghostprotocols.net> (raw)
In-Reply-To: <20101125154718.GE15875@ghostprotocols.net>

Em Thu, Nov 25, 2010 at 01:47:18PM -0200, Arnaldo Carvalho de Melo escreveu:
> Em Tue, Nov 23, 2010 at 10:41:21AM -0200, Arnaldo Carvalho de Melo escreveu:
> > Em Tue, Nov 23, 2010 at 12:08:32PM +0100, Peter Zijlstra escreveu:
> > > Right, so acme had a patch adding:
> > > PERF_SAMPLE_{TID,TIME,ID,CPU,STREAM_ID}

> I know of a problem with unconditionally stting attr->sample_type_all
> and then trying the new perf tool on an older kernel, that will fail
> with:
> [root@felicio ~]# perf record -a -g
>   Error: sys_perf_event_open() syscall returned with -1 (Invalid
> argument).  /bin/dmesg may provide additional information.
>   Fatal: No CONFIG_PERF_EVENTS=y kernel support configured?
> 
> Because it doesn't expects that extra bit to be set. I'll use that to
> make sure the binary works on older kernels without this feature.

This got fixed.

http://git.kernel.org/?p=linux/kernel/git/acme/linux-2.6.git;a=shortlog;h=refs/heads/perf/sample_id_all.v1

Has the latest, that I was about to submit but I'll change it so that
older perf tools can cope with newer perf.data files, by stashing the
new fields after the existing layout, not between perf_event_header and
the mmap/fork/comm/etc specific stuff.

I'll rework that, test newer perf.data files with older perf tools and
then submit.

Thanks,

- Arnaldo

  reply	other threads:[~2010-11-26 21:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23  5:35 perf: Timestamp COMM and MMAP events for correct attribution Ian Munsie
2010-11-23  5:35 ` [PATCH 1/6] perf: Display unknown rather than IP for unidentified DSO Ian Munsie
2010-11-23  5:35 ` [PATCH 2/6] perf: Move all output for perf report -D into trace_event Ian Munsie
2010-11-23  5:35 ` [PATCH 3/6] perf: Add timestamp to COMM and MMAP events Ian Munsie
2010-11-23 11:08   ` Peter Zijlstra
2010-11-23 12:41     ` Arnaldo Carvalho de Melo
2010-11-25 15:47       ` Arnaldo Carvalho de Melo
2010-11-26 21:54         ` Arnaldo Carvalho de Melo [this message]
2010-11-29  6:06         ` Ian Munsie
2010-11-29 11:54           ` Peter Zijlstra
2010-11-29 23:45             ` Ian Munsie
2010-11-30 14:02               ` Arnaldo Carvalho de Melo
2010-11-23  5:35 ` [PATCH 4/6] perf: Add timestamp to READ and LOST events Ian Munsie
2010-11-23  5:35 ` [PATCH 5/6] perf tool: Process COMM and MMAP events in order Ian Munsie
2010-11-23  5:35 ` [PATCH 6/6] perf tool: Process READ and LOST " Ian Munsie
2010-11-23  6:37 ` perf: Timestamp COMM and MMAP events for correct attribution Ian Munsie

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=20101126215430.GA23996@ghostprotocols.net \
    --to=acme@ghostprotocols.net \
    --cc=a.p.zijlstra@chello.nl \
    --cc=imunsie@au1.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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