From: David Ahern <dsahern@gmail.com>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
ak@linux.intel.com, Stephane Eranian <eranian@google.com>
Subject: Re: Does perf inject preserve call chain data?
Date: Fri, 08 Jun 2012 11:13:27 -0600 [thread overview]
Message-ID: <4FD232B7.7080905@gmail.com> (raw)
In-Reply-To: <1339173896.3796.230.camel@schen9-DESK>
On 6/8/12 10:44 AM, Tim Chen wrote:
> On Fri, 2012-06-08 at 11:38 -0300, Arnaldo Carvalho de Melo wrote:
>> Em Tue, May 22, 2012 at 03:58:40PM -0600, David Ahern escreveu:
>>> On 5/22/12 12:49 PM, Tim Chen wrote:
>>>> Arnaldo,
>>>>
>>>> Wonder if perf inject munged the call chain data from perf record?
>>>>
>>>> When I do
>>>> perf record -a -g -o - sleep 5 |perf inject -v -b | perf report -g -i -
>>>> I get a complain from perf report
>>>>
>>>> Warning:
>>>> Selected -g but no callchain data. Did you call 'perf record' without -g?
>>>>
>>>
>>> I believe the root cause is that the event list is not written to
>>> the pipe. Using Arnaldo's git repo as of today (has fixes from
>>> Stephane) this hack shows the info is there and can be processed.
>>
>> How things stand here? Tim, did this fix things for you? If so, David,
>> please resend with a proper subject line and a Tested-by: Tim, ok?
>>
>> Thanks,
>>
>> - Arnaldo
>>
>
> It didn't fix things for me when I was testing on a westmere-ex machine.
> I got
>
> # ./perf record -a -g -o - sleep 5 |perf inject -v -b | perf report -g -i -
> incompatible file format
> incompatible file formatincompatible file formatselected -g but no callchain data. Did you call perf record without -g?
>
> Testing was done on 3.5.0-rc1.
Is ./ needed in front of the second and third invocations are do you
have ./ in the PATH?
David
next prev parent reply other threads:[~2012-06-08 17:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 18:49 Does perf inject preserve call chain data? Tim Chen
2012-05-22 21:58 ` David Ahern
2012-06-08 14:38 ` Arnaldo Carvalho de Melo
2012-06-08 16:44 ` Tim Chen
2012-06-08 17:13 ` David Ahern [this message]
2012-06-08 17:17 ` Tim Chen
2012-06-08 19:52 ` Andi Kleen
2012-06-09 16:05 ` Arnaldo Carvalho de Melo
2012-06-11 18:43 ` Andi Kleen
2012-06-11 19:11 ` David Ahern
2012-06-11 21:59 ` Arnaldo Carvalho de Melo
2012-06-11 22:11 ` Andi Kleen
2012-06-12 0:02 ` Arnaldo Carvalho de Melo
2012-06-11 18:23 ` 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=4FD232B7.7080905@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.c.chen@linux.intel.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