From: chenggang qin <chenggang.qin@gmail.com>
To: linux-perf-users@vger.kernel.org
Subject: Re: How to trace threads created by a process after perf has started recording, using the -p PID flag?
Date: Sun, 26 Aug 2012 12:56:19 +0800 [thread overview]
Message-ID: <5039AC73.8090908@gmail.com> (raw)
In-Reply-To: <CAJgLYc+dMADVBkbPq1wJFptcx63UUSg24DDM5BbYSWW2bDV+tg@mail.gmail.com>
HI:
I submitted a patch to fix this problem. and the patch is waitting for
reviewing.
chenggang qin
On Sat, Aug 25, 2012 at 8:52 PM, Mikolaj Konarski <
mikolaj.konarski@gmail.com> wrote:
> Hi,
>
> Could someone clarify the behaviour of the -p PID flag of perf-record?
> In our experiments (3.2.0-27 #43-Ubuntu SMP x86_64),
> it ignores events on threads spawned after perf-record is started.
> Is this the intended behaviour, and is there any work-around?
>
> Generally, what is the best (vs CPU/IO, distortion of profiling results)
> way to record only events of a given OS process, with all its threads?
>
> Thanks a lot,
> Mikolaj
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next parent reply other threads:[~2012-08-26 4:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJgLYc+dMADVBkbPq1wJFptcx63UUSg24DDM5BbYSWW2bDV+tg@mail.gmail.com>
2012-08-26 4:56 ` chenggang qin [this message]
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
2012-09-22 19:57 ` Mikolaj Konarski
2012-09-24 4:31 ` 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=5039AC73.8090908@gmail.com \
--to=chenggang.qin@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).