From: David Ahern <dsahern@gmail.com>
To: Adrian Hunter <adrian.hunter@intel.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 07:45:57 -0600 [thread overview]
Message-ID: <5225E815.4010705@gmail.com> (raw)
In-Reply-To: <5225E320.8090307@intel.com>
On 9/3/13 7:24 AM, Adrian Hunter wrote:
> On 03/09/13 15:50, David Ahern wrote:
>> 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?
Both throw the same error. Command line used to create the file:
perf record -e raw_syscalls:* -e sched:* -p 2271 -g -- sleep 5
David
next prev parent reply other threads:[~2013-09-03 13:46 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
2013-09-03 13:45 ` David Ahern [this message]
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=5225E815.4010705@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=adrian.hunter@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.