linux-kernel - Re: [PATCH] printk timestamp post-boot suppression, v2

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

Message-ID: <20080828094032.GC28783@elte.hu>
Date:	Thu, 28 Aug 2008 11:40:32 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Joe Korty <joe.korty@...r.com>
Cc:	Mark Brown <broonie@...ena.org.uk>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Simon Farnsworth <simon.farnsworth@...lan.com>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: [PATCH] printk timestamp post-boot suppression, v2


* Joe Korty <joe.korty@...r.com> wrote:

> On Wed, Aug 27, 2008 at 12:16:30PM -0400, Mark Brown wrote:
> > It'd be nicer if this were optional - syslog typically only logs at
> > second resolution and not all systems are going to have logfiles.
> 
> Optionally suppress printk timestamping after system boot.

i think the best approach is to write an initcall tracer - i think Arjan 
has some ideas in that area.

that would be infinitely higher quality than anything printk based 
anyway, as with ftrace you could see the reasons of why a boot delay 
happens - which tasks context-switch, in which code path, etc.

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