From: Adrian Hunter <adrian.hunter@intel.com>
To: David Ahern <dsahern@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: latest perf code fails to parse existing data file
Date: Tue, 03 Sep 2013 16:24:48 +0300 [thread overview]
Message-ID: <5225E320.8090307@intel.com> (raw)
In-Reply-To: <5225DAFB.1070406@gmail.com>
On 03/09/13 15:50, David Ahern wrote:
> On 9/3/13 12:40 AM, Adrian Hunter wrote:
>> On 03/09/13 00:37, David Ahern wrote:
>>> Arnaldo/Adrian:
>>>
>>> Latest acme core tree fails to parse an existing data file:
>>>
>>> $ perf trace -i perf.data
>>> 0x16b8 [0x40]: failed to process type: 1
>>> Failed to process events, error -22
>>
>> I can't reproduce this. The following works:
>>
>> $ perf --version
>> perf version 3.9.10-100.fc17.x86_64
>> $ sudo perf record -e raw_syscalls:* ls
>> ...
>> $ tools/perf/perf --version
>> perf version 3.11.rc4.g31cd38
>> $ sudo tools/perf/perf script
>> ...
>> $ sudo tools/perf/perf trace -i perf.data
>> ...
>
> Kernel version? Is your kernel side support there?
The kernel version is the same as the perf version i.e. 3.9
>
> For me data was collected on 2.6.34 about a week ago. Processed fine up to
> the point of this patch getting added.
Is it only "perf trace" that fails or does "perf script" fail too?
next prev parent reply other threads:[~2013-09-03 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 21:37 latest perf code fails to parse existing data file David Ahern
2013-09-03 6:40 ` Adrian Hunter
2013-09-03 12:50 ` David Ahern
2013-09-03 13:24 ` Adrian Hunter [this message]
2013-09-03 13:45 ` David Ahern
2013-09-04 17:54 ` 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=5225E320.8090307@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.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