public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: davidm@hpl.hp.com
Cc: arjanv@redhat.com, davem@redhat.com, ak@muc.de,
	johnstul@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: time interpolation hooks
Date: Mon, 19 May 2003 11:57:09 -0700	[thread overview]
Message-ID: <20030519115709.0701a1c3.akpm@digeo.com> (raw)
In-Reply-To: <16073.9205.641605.741130@napali.hpl.hp.com>

David Mosberger <davidm@napali.hpl.hp.com> wrote:
>
> Andrew, I assume it's OK with you if I update the ia64 code to the
>  proposed interface and then send you an updated patch?

Sure.  It's be good to see an ia32 implementation which can be beaten on. 
Maybe John can look into that?

>From an implementation point of view, I wonder if all platforms will need
the indirection?

If not then it would be better to just do

	update_wall_time_hook(sys_tz.tz_minuteswest * 60 * NSEC_PER_SEC);

in kernel/time.c and let the architecture decide whether it wants to add
the extra overwriteable hooks.

So include/asm/time-interpolation.h has:

	#include <asm-generic/time-interpolation.h>

and asm-generic/time-interpolation.h has:

	struct time_interpolator {
		...
	}

	static inline void update_wall_time_hook(unsigne long nsec)
	{
		time_interpolator.update_wall_time(nsec);
	}

if you get my drift.



  reply	other threads:[~2003-05-19 18:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16 21:23 time interpolation hooks Andrew Morton
2003-05-16 22:00 ` David Mosberger
2003-05-17  2:38   ` David S. Miller
2003-05-19 17:34     ` David Mosberger
2003-05-19 17:42       ` Arjan van de Ven
2003-05-19 18:35         ` David Mosberger
2003-05-19 18:57           ` Andrew Morton [this message]
2003-05-20  7:26             ` David Mosberger
2003-05-19 22:37       ` David S. Miller
2003-05-19 23:03         ` David Mosberger
2003-05-19 23:08           ` David S. Miller
2003-05-17  9:09 ` Arjan van de Ven
2003-05-17 16:31 ` john stultz
2003-05-17 16:37   ` john stultz

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=20030519115709.0701a1c3.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=ak@muc.de \
    --cc=arjanv@redhat.com \
    --cc=davem@redhat.com \
    --cc=davidm@hpl.hp.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    /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