mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Remy Bohmer" <l.pinguin@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>,
	RT-Users <linux-rt-users@vger.kernel.org>
Cc: mathieu.desnoyers@polymtl.ca, "Ingo Molnar" <mingo@elte.hu>
Subject: [Question] Hooks for scheduler tracing (CFS)
Date: Mon, 16 Jul 2007 21:46:46 +0200	[thread overview]
Message-ID: <3efb10970707161246se06ab22i32872cfe6fa4f2f6@mail.gmail.com> (raw)

Hello,

I am looking for some tool/kernel machanism that enables me to track
every schedule change on the CFS scheduler of the RT-kernel for some
period of time.
Thus a tool that gives me an overview after some time which task got
"scheduled in/out" at "which timestamp" and at "which CPU". ( I need
the raw data)

In a far past (on Montavista kernels) I used LTT for this to log for
some time with only the SCHED_CHANGE filter and text output. But, I
cannot find any LTT(ng) support for any RT-kernel, and support for the
new CFS (like in 2.6.22.1-rt4) is even harder.

So I was wondering if anybody knows some tool/kernel mechanism which
can do this?
If not, I will build a kernel extension for it myself (new extension
to 'latency_trace' ?)
In that case can anybody with in depth CFS scheduler knowledge please
point me which hooks are safe to use for this?

I need it to get a detailed insight in my RT-system with its RT and
non-RT applications.
Thus to know when a certain task gets scheduled (and to calculate its
per thread min/max/avg latencies), which task preempts another task,
and to get a complete overview of what the RT system (and scheduler)
is doing during time etc.


Kind Regards,

Remy Böhmer

             reply	other threads:[~2007-07-16 19:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16 19:46 Remy Bohmer [this message]
2007-07-16 19:52 ` Arjan van de Ven
2007-07-16 20:17   ` Remy Bohmer
2007-07-16 21:12     ` Ingo Molnar
2007-07-26  7:28   ` Ankita Garg
2007-07-26  7:35     ` Ingo Molnar
2007-07-26  7:49       ` Ankita Garg
2007-07-26  7:53         ` Ingo Molnar
2007-07-26  9:59           ` Ankita Garg
2007-07-26 11:05             ` Ingo Molnar
2007-07-26 13:06               ` Mathieu Desnoyers
2007-07-26 17:45                 ` David J. Wilder
2007-07-26 18:30                   ` Mathieu Desnoyers
2007-07-26 13:20               ` Ankita Garg
2007-07-26 13:31     ` Mathieu Desnoyers
2007-07-26 14:47       ` Frank Ch. Eigler
2007-07-26 15:02         ` Mathieu Desnoyers
2007-07-26 16:22           ` Frank Ch. Eigler
2007-07-26 16:32             ` Ankita Garg
2007-07-26 18:25             ` Mathieu Desnoyers
2007-07-26 15:17         ` Arnaldo Carvalho de Melo
2007-07-16 20:07 ` Mathieu Desnoyers
2007-07-16 23:03 ` LTTng for 2.6.22.1-rt4 Mathieu Desnoyers
     [not found]   ` <3efb10970707170034t3e1dabe5wc70d41f6ab209c7e@mail.gmail.com>
2007-07-17 14:45     ` LTTng for 2.6.22.1-rt4 (timestamping) Mathieu Desnoyers
2007-07-17  7:23 ` [Question] Hooks for scheduler tracing (CFS) Sébastien Dugué

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=3efb10970707161246se06ab22i32872cfe6fa4f2f6@mail.gmail.com \
    --to=l.pinguin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=linux@bohmer.net \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    /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

all inboxes | Powered by JetHome®