All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Frédéric Weisbecker" <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Steven Noonan <steven@uplinklabs.net>,
	Arjan van de Ven <arjan@infradead.org>
Subject: [Patch -tip 0/4] Creation of the initcall tracer
Date: Tue, 23 Sep 2008 11:29:42 +0100	[thread overview]
Message-ID: <48D8C516.4090706@gmail.com> (raw)

This patchset is about the initcall tracer requested by Ingo Molnar.
It is supposed to replace the printk involved during fastboot if the initcall_debug parameter has been selected.

Currently this tracer is a test. Its output is not yet adapted for scripts/bootgraph.pl which uses the old initcalls printk to produce a graph. But since this tracer will output sched_switch and stack_trace, we should first talk about the future output format of this tracer in sync with bootgraph.pl

It currently not uses the sched_switch and stack_trace tracers since related functions of insertion into the ring buffer perhaps need first to be moved on their own tracer file. But it have to be discussed.

Note that you need the initcall_debug to enable this tracer. When printk from initcall_debug will disappear, we could surely enable this tracer by default without this parameter.

Old printk have been kept for backward compatibility.

Please don't hesitate to give any comment.

Thanks.

Frédéric Weisbecker.

             reply	other threads:[~2008-09-23  9:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23 10:29 Frédéric Weisbecker [this message]
2008-09-23 10:00 ` [Patch -tip 0/4] Creation of the initcall tracer Ingo Molnar
2008-09-23 11:42   ` Frédéric Weisbecker
2008-09-23 19:31   ` Ingo Molnar
2008-09-24  9:36     ` Frédéric Weisbecker
2008-09-24  8:58       ` Ingo Molnar

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=48D8C516.4090706@gmail.com \
    --to=fweisbec@gmail.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=steven@uplinklabs.net \
    /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.