From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: john stultz <johnstul@us.ibm.com>
Cc: Richard Henderson <rth@twiddle.net>,
lkml <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Matt Turner <mattst88@gmail.com>
Subject: Re: [RFC][PATCH] Convert alpha to use clocksource
Date: Fri, 19 Mar 2010 00:40:30 +0300 [thread overview]
Message-ID: <20100318214030.GA8934@jurassic.park.msu.ru> (raw)
In-Reply-To: <1268934923.1855.8.camel@work-vm>
On Thu, Mar 18, 2010 at 10:55:23AM -0700, john stultz wrote:
> On Thu, 2010-03-18 at 07:32 -0700, Richard Henderson wrote:
> > On 03/17/2010 07:01 PM, John Stultz wrote:
> > > Alpha has a tsc like rpcc counter that it uses to manage time.
> > > This can be converted to an actual clocksource instead of utilizing
> > > the arch_gettimeoffset method that is really only there for legacy
> > > systems with no continuous counter.
> >
> > With 8 seconds or less between roll-overs, do you actually consider
> > this a continuous counter? I don't. I suggest this be left alone.
>
> The timekeeping code handles this (although the shift value I picked may
> need some adjustment - what is the expected counter freq range on
> alpha?). The ACPI PM counter which is very common on x86 is only 24 bits
> and rolls over in ~5 seconds. It works fine.
Yeah, that looks cool. I'm typing this on the 800MHz UP1500 running
2.6.34-rc1 plus your patch, and the timekeeping works fine so far.
Though, even after a glance over the clocksource code, I've not
gotten yet to how one could estimate the "shift" value...
Any hints?
And if I recall correctly, production alphas have been clocked
in the range of 60-1250 MHz.
Ivan.
next prev parent reply other threads:[~2010-03-18 22:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 2:01 John Stultz
2010-03-18 14:32 ` Richard Henderson
2010-03-18 17:55 ` john stultz
2010-03-18 21:40 ` Ivan Kokshaysky [this message]
2010-03-18 22:19 ` john stultz
2010-03-19 10:07 ` Ivan Kokshaysky
2010-03-19 16:47 ` Matt Turner
2010-03-19 17:13 ` Richard Henderson
2010-03-22 11:17 ` Johannes Weiner
2010-03-22 14:22 ` Thomas Gleixner
2010-03-22 16:41 ` Johannes Weiner
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=20100318214030.GA8934@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=rth@twiddle.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®