linux-kernel - [Patch -tip 0/4] Creation of the initcall tracer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <48D8C516.4090706@gmail.com>
Date:	Tue, 23 Sep 2008 11:29:42 +0100
From:	Frédéric Weisbecker <fweisbec@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>,
	Steven Noonan <steven@...inklabs.net>,
	Arjan van de Ven <arjan@...radead.org>
Subject: [Patch -tip 0/4] Creation of the initcall tracer

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/