Date: Thu, 28 Aug 2008 11:40:32 +0200
From: Ingo Molnar <mingo@elte.hu>
To: Joe Korty <joe.korty@ccur.com>
Cc: Mark Brown <broonie@sirena.org.uk>,
       Linux Kernel <linux-kernel@vger.kernel.org>,
       Simon Farnsworth <simon.farnsworth@onelan.com>,
       Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH] printk timestamp post-boot suppression, v2
Message-ID: <20080828094032.GC28783@elte.hu>
References: <20080827151613.GA10325@tsunami.ccur.com> <20080827161621.GF10834@sirena.org.uk> <20080827170424.GA17217@tsunami.ccur.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080827170424.GA17217@tsunami.ccur.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 868
Lines: 22


* Joe Korty <joe.korty@ccur.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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/