public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Andi Kleen <ak@muc.de>, Arjan van de Ven <arjanv@redhat.com>,
	john stultz <johnstul@us.ibm.com>,
	linux-kernel@vger.kernel.org,
	David Mosberger <davidm@napali.hpl.hp.com>
Subject: Re: time interpolation hooks
Date: Sat, 17 May 2003 09:09:51 +0000	[thread overview]
Message-ID: <20030517090951.D31765@devserv.devel.redhat.com> (raw)
In-Reply-To: <20030516142311.3844ee97.akpm@digeo.com>; from akpm@digeo.com on Fri, May 16, 2003 at 02:23:11PM -0700

On Fri, May 16, 2003 at 02:23:11PM -0700, Andrew Morton wrote:

I rather would have a "timer source" object that
provides those 2 functions as methods, so that one can write "timer" drivers
as more or less stand alone units that register themselves
with the generic timekeeping unit (probably with an accuracy score so that
the generic code can pick one in the event of multiple timer sources). 
For x86 I wrote an acpitimer "driver" last week (for 2.4) and it
gets messy if you have those 2 functions as just independent
function pointers ....

  parent reply	other threads:[~2003-05-17  8:57 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
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 [this message]
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=20030517090951.D31765@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=ak@muc.de \
    --cc=akpm@digeo.com \
    --cc=davidm@napali.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