All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Thu, 28 Aug 2008 11:40:32 +0200	[thread overview]
Message-ID: <20080828094032.GC28783@elte.hu> (raw)
In-Reply-To: <20080827170424.GA17217@tsunami.ccur.com>


* 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

      parent reply	other threads:[~2008-08-28  9:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27 15:16 [PATCH] printk timestamp post-boot suppression Joe Korty
2008-08-27 15:26 ` Simon Farnsworth
2008-08-27 16:16 ` Mark Brown
2008-08-27 17:04   ` [PATCH] printk timestamp post-boot suppression, v2 Joe Korty
2008-08-27 17:13     ` Simon Farnsworth
2008-08-27 17:22       ` Joe Korty
2008-08-27 17:27         ` Joe Korty
2008-08-27 17:22     ` Andi Kleen
2008-08-28  9:40     ` Ingo Molnar [this message]

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=20080828094032.GC28783@elte.hu \
    --to=mingo@elte.hu \
    --cc=arjan@infradead.org \
    --cc=broonie@sirena.org.uk \
    --cc=joe.korty@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simon.farnsworth@onelan.com \
    /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.