From: jbaron@redhat.com (Jason Baron)
Subject: [ltt-dev] [patch] add tracepoints to trace activate/deactivate task
Date: Mon, 8 Dec 2008 17:38:40 -0500 [thread overview]
Message-ID: <20081208223840.GA30314@redhat.com> (raw)
In-Reply-To: <1228766050.6939.7.camel@twins>
On Mon, Dec 08, 2008 at 08:54:10PM +0100, Peter Zijlstra wrote:
> On Mon, 2008-12-08 at 14:49 -0500, Jason Baron wrote:
> > hi,
> >
> > I thought it would be useful to track when a task is
> > 'activated/deactivated'. This case is different from wakeup/wait, in that
> > task can be activated and deactivated, when the scheduler re-balances
> > tasks, the allowable cpuset changes, or cpu hotplug occurs. Using these
> > patches I can more precisely figure out when a task becomes runnable and
> > why.
>
> Then I still not agree with it because it does not expose the event that
> did the change.
>
> If you want the cpu allowed mask, put a tracepoint there. If you want
> migrate information (didn't we have that?) then put one there, etc.
>
well, with stap backtrace I can figure out the event, otherwise i'm
sprinkling 14 more trace events in the scheduler...I can go down that
patch if people think its better?
thanks,
-Jason
next prev parent reply other threads:[~2008-12-08 22:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 19:49 Jason Baron
2008-12-08 19:54 ` Peter Zijlstra
2008-12-08 22:38 ` Jason Baron [this message]
2008-12-08 22:42 ` Peter Zijlstra
2008-12-09 21:00 ` Jason Baron
2008-12-09 21:29 ` Jason Baron
2008-12-09 22:10 ` Mathieu Desnoyers
2008-12-10 7:08 ` Peter Zijlstra
2008-12-10 12:27 ` Mathieu Desnoyers
2008-12-10 13:15 ` Peter Zijlstra
2008-12-10 17:14 ` Jason Baron
2008-12-10 17:52 ` Mathieu Desnoyers
2008-12-10 19:28 ` Peter Zijlstra
2008-12-10 12:34 ` Mathieu Desnoyers
2008-12-10 13:14 ` Peter Zijlstra
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=20081208223840.GA30314@redhat.com \
--to=jbaron@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox