From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: tony.luck@intel.com, linux-kernel@vger.kernel.org, jasonuhl@sgi.com
Subject: Re: CONFIG_PRINTK_TIME woes
Date: Sun, 21 Aug 2005 19:27:17 +1000 [thread overview]
Message-ID: <430848F5.3040308@yahoo.com.au> (raw)
In-Reply-To: <20050821021616.6bbf2a14.akpm@osdl.org>
Andrew Morton wrote:
> Andrew Morton <akpm@osdl.org> wrote:
>
>>How about we give each arch a printk_clock()?
>
>
> Which might be as simple as this..
>
>
sched_clock() shouldn't really be taken outside kernel/sched.c,
especially for things like this.
It actually has some fundamental problems even in its current
use in the scheduler (which need to be fixed). But basically it
is a very nasty interface with a rather tenuous relationship to
time.
Why not use something like do_gettimeofday? (or I'm sure one
of our time keepers can suggest the right thing to use).
Nick
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2005-08-21 9:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 18:47 CONFIG_PRINTK_TIME woes Luck, Tony
2005-08-21 9:13 ` Andrew Morton
2005-08-21 9:16 ` Andrew Morton
2005-08-21 9:27 ` Nick Piggin [this message]
2005-08-21 9:32 ` Andrew Morton
2005-08-21 11:25 ` Nick Piggin
2005-08-21 18:01 ` Andrew Morton
2005-08-24 0:04 ` Tim Bird
2005-08-22 17:42 ` tony.luck
2005-08-22 17:50 ` Andrew Morton
2005-08-22 20:52 ` tony.luck
2005-08-22 20:20 ` David S. Miller
2005-08-22 20:33 ` Jason Uhlenkott
2005-08-22 20:42 ` David S. Miller
2005-08-22 21:15 ` Andrew Morton
2005-08-22 22:33 ` tony.luck
2005-08-22 22:38 ` Andrew Morton
2005-08-22 23:27 ` tony.luck
2005-08-23 1:52 ` Paul Mackerras
2005-08-23 15:01 ` Nick Piggin
2005-08-22 21:10 ` tony.luck
2005-08-24 0:36 ` Tim Bird
2005-08-23 7:18 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2005-08-23 14:07 Luck, Tony
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=430848F5.3040308@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=jasonuhl@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox