All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Rune Torgersen <runet@innovsys.com>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: RE: Override timer interrupt
Date: Tue, 16 Oct 2007 07:58:18 +1000	[thread overview]
Message-ID: <1192485498.11795.41.camel@pasglop> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B037D5152@ismail.innsys.innovsys.com>


On Mon, 2007-10-15 at 16:50 -0500, Rune Torgersen wrote:
> Huh? Not in 2.6.18/arch/ppc at least, unless I'm completely
> misundrstanding the code.
> ppc/powerpc seems to be using clocksource_jiffies as the clock source,
> and teh gettimeofday gets xtime + a offset from last jiffie, and xtime
> is updated with a fixed amount per tick.
> 
> Things have changed a lot since I last delved deep into this to try to
> ge an accurate freerunning clock (2.6.12).

Hrm... 2.6.18 doesn't have clock sources in the first place, what kernel
are you using ?

Ben.

  reply	other threads:[~2007-10-15 21:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12 20:43 Override timer interrupt Rune Torgersen
2007-10-12 21:30 ` Mark A. Greer
2007-10-12 21:39   ` Rune Torgersen
2007-10-12 21:55     ` Mark A. Greer
2007-10-12 22:58     ` Benjamin Herrenschmidt
2007-10-15 16:49       ` Rune Torgersen
2007-10-15 20:55         ` Benjamin Herrenschmidt
2007-10-15 21:50           ` Rune Torgersen
2007-10-15 21:58             ` Benjamin Herrenschmidt [this message]
2007-10-15 23:30         ` Paul Mackerras
  -- strict thread matches above, loose matches on Subject: below --
2007-10-12 20:49 Rune Torgersen
2007-10-12 21:32 ` Mark A. Greer

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=1192485498.11795.41.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=runet@innovsys.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.