From: Frederic Weisbecker <fweisbec@gmail.com>
To: David Ahern <dsahern@gmail.com>
Cc: Arun Sharma <asharma@fb.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Using a new perf tool against an older kernel
Date: Fri, 24 Jun 2011 02:11:48 +0200 [thread overview]
Message-ID: <20110624001145.GE8058@somewhere.redhat.com> (raw)
In-Reply-To: <4E039BC7.4050802@gmail.com>
On Thu, Jun 23, 2011 at 02:02:15PM -0600, David Ahern wrote:
>
>
> On 06/23/2011 01:39 PM, Arun Sharma wrote:
> > On 6/23/11 7:22 AM, David Ahern wrote:
> >
> >> I have not seen issues like this using newer perf userspace against
> >> older kernels. For example, my laptop was running Fedora 14 (2.6.35) and
> >> now Fedora 15 (2.6.38.8) and I typically use latest perf builds (e.g.,
> >> testing patches).
> >
> > I narrowed it down to PERF_SAMPLE_RAW:
> >
> > perf record -ag -- sleep 1
> >
> > is fine, but:
> >
> > perf record -agR -- sleep 1
> >
> > fails for me most of the time. The reason I needed to use the -R in the
> > first place is that "perf script" fails on older kernels with:
> >
> > Samples do not contain timestamps.
> >
> > With the newer perf, I don't get errors, but the timestamp field is
> > invalid. So I need to use the -R flag to get valid timestamps +
> > stacktraces out of "perf script".
>
> That should have been fixed.
>
> And -T on record gets the timestamps.
>
> David
Right, it would be nice to suggest that from perf script when timestamps
are not recorded.
next prev parent reply other threads:[~2011-06-24 0:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 21:39 Using a new perf tool against an older kernel Arun Sharma
2011-06-23 14:22 ` David Ahern
2011-06-23 19:39 ` Arun Sharma
2011-06-23 20:02 ` David Ahern
2011-06-24 0:11 ` Frederic Weisbecker [this message]
2011-06-24 5:14 ` David Ahern
2011-06-24 0:11 ` Frederic Weisbecker
2011-06-24 0:43 ` Arun Sharma
2011-06-24 5:07 ` 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=20110624001145.GE8058@somewhere.redhat.com \
--to=fweisbec@gmail.com \
--cc=asharma@fb.com \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@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.