linux-kernel - Re: [PATCH] tracing/fastboot: document the need of initcall

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4A488304.9000104@cn.fujitsu.com>
Date:	Mon, 29 Jun 2009 17:01:56 +0800
From:	Li Zefan <lizf@...fujitsu.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Frederic Weisbecker <fweisbec@...il.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tracing/fastboot: document the need of initcall_debug

Ingo Molnar wrote:
> * Li Zefan <lizf@...fujitsu.com> wrote:
> 
>> To use boot tracer, one should pass initcall_debug as well as
>> ftrace=initcall to the command line.
> 
> I think both should be auto-enabled if BOOT_TRACER is enabled, for 
> ease of use - agreed?
> 

If both are auto-enabled, we'll always do boot tracing. But we want
BOOT_TRACER to be enabled and only enable boot tracing when it's needed.

But maybe we can make ftrace=initcall implies initcall_debug=1?

--
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/