mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: Jack Harvard <jack.harvard@googlemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: gettimeofday() in 2.6.24
Date: Fri, 18 Apr 2008 08:35:52 -0600	[thread overview]
Message-ID: <4808B1C8.2060601@nortel.com> (raw)
In-Reply-To: <a72f6a3c0804180154x28d0b528gc1cbd3d11279c4a1@mail.gmail.com>

Jack Harvard wrote:
> On Thu, Apr 17, 2008 at 7:13 PM, Chris Friesen <cfriesen@nortel.com>
> wrote:

>> system_timer->offset() uses the added timer to return the number of
>> usecs since the last timer tick.  It's potentially different for
>> each specific type of arm blade, and the function often has
>> "gettimeoffset" in the name.

>> "xtime" is updated in the core kernel code.


> is "xtime" updated by the time tick clock timer, i.e., the timer
> which generates interrupts every 1/HZ second to the kernel. Put it in
>  another way, does gettimeofday get time in two parts 1) seconds from
> xtime.tv_sec, updated by timer0, 2) microseconds from xtime.tv_nsec +
>  system_timer->offset(), updated by timer0 and timer3.

Yes, I think xtime is updated by the tick timer.

system_timer->offset() may be updated by different mechanisms, depending 
on the specific arm subarch.

> Do you mean the code here 
> "http://lxr.linux.no/linux+v2.6.24/kernel/time/timekeeping.c#L45"

No.  As I said, the function usually has "gettimeoffset" in the name and 
it's specific to arm so it would be under arch/arm.  For instance, on 
Xscale boards it's ixp2000_gettimeoffset() in arch/arm/mach-ixp2000/core.c.

For more information you might want to look at the code in arch/arm or 
else talk to the arm developers on the linux-arm-kernel mailing list.

Chris

      reply	other threads:[~2008-04-18 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-17 17:31 Jack Harvard
2008-04-17 18:13 ` Chris Friesen
2008-04-18  8:54   ` Jack Harvard
2008-04-18 14:35     ` Chris Friesen [this message]

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=4808B1C8.2060601@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=jack.harvard@googlemail.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

Powered by JetHome