All of lore.kernel.org
 help / color / mirror / Atom feed
From: john cooper <john.cooper@third-harmonic.com>
To: dwalker@mvista.com
Cc: Kevin Hilman <khilman@mvista.com>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org,
	john cooper <john.cooper@third-harmonic.com>
Subject: Re: 2.6.18-rt7: rollover with 32-bit cycles_t
Date: Wed, 08 Nov 2006 08:29:04 -0500	[thread overview]
Message-ID: <4551DBA0.6080305@third-harmonic.com> (raw)
In-Reply-To: <1162956221.20694.13.camel@dwalker1.mvista.com>

Daniel Walker wrote:

> Seems like the check should really be using something like time_before()
> time_after() which takes the rollover into account .. What I don't
> understand is why we don't see those on x86 ..

Probably due to the fact it is a 64-bit counter.  Even with
a free running rate of 10Ghz it would take nearly 60 years
to wrap.

On PPC and ARM 32-bit counters seems to be common which limits
range unless a prescaler is available.  The better solution is
to detect wrap as a prescaled 32 bit measurement will eventually
run out of usable resolution as core frequency increases.  That is
assuming 64-bit counters don't eventually show up in these
architectures.

-john

-- 
john.cooper@third-harmonic.com

      reply	other threads:[~2006-11-08 13:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08  1:36 2.6.18-rt7: rollover with 32-bit cycles_t Kevin Hilman
2006-11-08  2:06 ` john cooper
2006-11-08 19:22   ` Kevin Hilman
2006-11-09  9:14     ` Ingo Molnar
2006-11-08  3:23 ` Daniel Walker
2006-11-08 13:29   ` john cooper [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=4551DBA0.6080305@third-harmonic.com \
    --to=john.cooper@third-harmonic.com \
    --cc=dwalker@mvista.com \
    --cc=khilman@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.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 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.