From: David Ahern <dsahern@gmail.com>
To: Mikolaj Konarski <mikolaj.konarski@gmail.com>
Cc: linux-perf-users@vger.kernel.org,
Bernie Pope <florbitous@gmail.com>,
Duncan Coutts <duncan@well-typed.com>
Subject: Re: How to trace threads created by a process after perf has started recording, using the -p PID flag?
Date: Sat, 22 Sep 2012 12:39:13 -0600 [thread overview]
Message-ID: <505E05D1.6090405@gmail.com> (raw)
In-Reply-To: <CAHFo2uq2pKx1FKSv5=mE7WhaqixJ2vzCSBxPeaz3DKE90vz0OQ@mail.gmail.com>
On 9/22/12 1:58 AM, Mikolaj Konarski wrote:
> Are we missing anything? Is the "--timestamp" option of perf-record
> related in any way? Any other tips?
That option adds the timestamps to the samples if it were not otherwise
added.
>
> We're working around right now by syncing with a timestamp
> of a known event, but that leaves us vulnerable to a time drift.
> If there's no way currently to generate externally meaningful
> timestamps, could we file a feature request for the sake of the future?
You mean like this: https://lkml.org/lkml/2011/6/7/638
David
next prev parent reply other threads:[~2012-09-22 18:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-25 12:52 How to trace threads created by a process after perf has started recording, using the -p PID flag? Mikolaj Konarski
[not found] ` <CAKYOsXwF-Rk97BEWk_fEHhfVisPy_q439tdx7H9onAOyFi=-uA@mail.gmail.com>
2012-09-03 22:17 ` Mikolaj Konarski
2012-09-04 6:47 ` Namhyung Kim
2012-09-04 16:04 ` David Ahern
2012-09-22 7:58 ` Mikolaj Konarski
2012-09-22 18:39 ` David Ahern [this message]
2012-09-22 19:57 ` Mikolaj Konarski
2012-09-24 4:31 ` David Ahern
[not found] <CAJgLYc+dMADVBkbPq1wJFptcx63UUSg24DDM5BbYSWW2bDV+tg@mail.gmail.com>
2012-08-26 4:56 ` chenggang qin
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=505E05D1.6090405@gmail.com \
--to=dsahern@gmail.com \
--cc=duncan@well-typed.com \
--cc=florbitous@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mikolaj.konarski@gmail.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 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.