From: Josh Stone <jistone@redhat.com>
To: David Juran <djuran@redhat.com>, systemtap@sourceware.org
Subject: Re: [PATCH] (Naive) approach to make schedtimes follow the children of the traced process
Date: Fri, 31 Jan 2014 16:19:00 -0000 [thread overview]
Message-ID: <52EBCD0A.1080302@redhat.com> (raw)
In-Reply-To: <1391165184.12098.9.camel@localhost.localdomain>
On 01/31/2014 02:46 AM, David Juran wrote:
> Hello!
>
> I had a use case where I wanted to investigate how much time a build
> process (in effect make) was spending waiting to be scheduled. The
> schedtimes exampel was a good match, but since I wanted to check both
> the make process itself but even more important, all the compile
> processes it forked off, I did some rather ugly extension to the
> schedtimes script.
> The modifications might come in useful for someone else as well but if
> you do consider taking the patch, please do review it. My approach of
> extending the script was rather simple...
Hi,
It's a reasonable modification, but you might like the target_set.stp
tapset to simplify it. Call function target_set_pid(some_pid) to find
out if it's part of the target() and its children.
Josh
next prev parent reply other threads:[~2014-01-31 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 10:46 David Juran
2014-01-31 16:19 ` Josh Stone [this message]
2014-02-03 12:07 ` David Juran
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=52EBCD0A.1080302@redhat.com \
--to=jistone@redhat.com \
--cc=djuran@redhat.com \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).