linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8xx: resolution of gettimeofday() ?
Date: Fri, 19 May 2006 10:55:13 -0700	[thread overview]
Message-ID: <20060519175513.GA12121@gate.ebshome.net> (raw)
In-Reply-To: <446D7CFA.5060505@imc-berlin.de>

On Fri, May 19, 2006 at 10:08:26AM +0200, Steven Scholz wrote:
> Eugene,
> 
> >> what is the resolution of gettimeofday() for an MPC8xx?
> >>
> >> IIUC then the "decrementer" is used to generate the timer interrupts every 10ms.
> >>
> >> This decrementer runs at cpuclk/16. Thus with 80MHz CPU clock has a
> >> resolution of 16/80MHz = 200ns and overflows every 50000 ticks.
> >>
> >> But is this decrementer used to update xtime?
> >> Will gettimeofday() have a resolution of 200ns?
> >>
> >> How about linux 2.4 where xtime is a "struct timeval" rather then "struct
> >> timespec"?
> >>
> > 
> > Usually on PPC we use timebase to interpolate time between Decrementer 
> > interrupts. In this case gettimeofday resolution is determined by 
> > timebase resolution which is quite high (megahertz range).
> 
> Sorry. I don't understand. What do you mean with "timebase"? Is there a
> second timer/counter?

PowerPC has a facility called timebase. This is 64-bit counter which 
can be accessed using special instructions (mftb, mftbu on 32-bit PPC).
Counter resolution depends on particular chip implementation, some 
use core clock, other use bus clock...

It's similar to the time-stamp counter in Intel CPUs (accessed 
with rdtsc instruction).

Please, refer to PPC arch manuals for more information. Also, if you 
really interested in how gettimeofday() is implemented, why don't you 
look at the source code yourself?

-- 
Eugene

  reply	other threads:[~2006-05-19 17:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18 15:10 MPC8xx: resolution of gettimeofday() ? Steven Scholz
2006-05-18 16:48 ` Eugene Surovegin
2006-05-19  8:08   ` Steven Scholz
2006-05-19 17:55     ` Eugene Surovegin [this message]
2006-05-22 11:03       ` Steven Scholz

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=20060519175513.GA12121@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=steven.scholz@imc-berlin.de \
    /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;
as well as URLs for NNTP newsgroup(s).