From: Andrew Morton <akpm@osdl.org>
To: Martin Peschke <mp3@de.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Patch 5/6] statistics infrastructure
Date: Tue, 30 May 2006 12:19:20 -0700 [thread overview]
Message-ID: <20060530121920.8c8f5d34.akpm@osdl.org> (raw)
In-Reply-To: <447C7E1F.7020602@de.ibm.com>
On Tue, 30 May 2006 19:17:19 +0200
Martin Peschke <mp3@de.ibm.com> wrote:
> Would I get away with making printk_clock() a timestamp_clock() that
> should be used by anyone exporting nsec_to_timestamp()-formated time
> stamps to user space, including me?
>
> I would then continue to see the use of sched_clock() in printk_clock()
> ... aehm timestamp_clock() as somebody else's problem (or at least
> as a subordinate problem).
Sure, a generic kernel-wide nsec-resolution timestamp_clock() makes sense
to me.
The default implementation can use sched_clock() but arch maintainers
can/should override it (vai attribute-weak) and do somethnig better.
next prev parent reply other threads:[~2006-05-30 19:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 12:33 Martin Peschke
2006-05-24 22:57 ` Andrew Morton
2006-05-29 22:17 ` Martin Peschke
2006-05-30 1:17 ` Andrew Morton
2006-05-29 22:17 ` [Patch] statistics infrastructure - update 1 Martin Peschke
2006-05-30 8:07 ` Heiko Carstens
2006-05-30 11:22 ` Martin Peschke
2006-05-30 17:17 ` [Patch 5/6] statistics infrastructure Martin Peschke
2006-05-30 19:19 ` Andrew Morton [this message]
2006-05-25 8:05 ` Nikita Danilov
2006-05-30 11:35 ` Martin Peschke
-- strict thread matches above, loose matches on Subject: below --
2006-05-19 16:13 Martin Peschke
2005-12-16 12:27 [patch " Martin Peschke
2005-12-14 16:46 Martin Peschke
2005-12-14 18:38 ` Andi Kleen
2005-12-16 1:00 ` Martin Peschke
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=20060530121920.8c8f5d34.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mp3@de.ibm.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
Powered by JetHome