From: john stultz <johnstul@us.ibm.com>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-rt21: slow-running clock
Date: Wed, 14 Dec 2005 17:41:36 -0800 [thread overview]
Message-ID: <1134610897.27117.4.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <200512140122.jBE1MZlE024707@auster.physics.adelaide.edu.au>
On Wed, 2005-12-14 at 11:52 +1030, Jonathan Woithe wrote:
> Hi John
>
> > On Fri, 2005-12-09 at 12:49 +1030, Jonathan Woithe wrote:
> > > > Ok, I went digging further and found the c3tsc selection is correct on
> > > > your hardware. I'm just too used to my own laptop where the TSC varies
> > > > with cpu speed and we lower the rating value. So that should be ok.
> > >
> > > Ok, good. That leaves the c3tsc slowdown as the only outstanding issue at
> > > this stage.
> > >
> > > > I'm now working on why we mis-compensate the c3tsc clocksource in the
> > > > -RT tree.
> > >
> > > No problem. Let me know when you have something to test or need further
> > > info.
> >
> > Attached is a test patch to see if it doesn't resolve the issue for
> > you. I get a maximum change in drift of 30ppm when idling between C3
> > states by being more careful with the C3 TSC compensation and I also
> > force timekeeping updates when cpufreq events occur.
>
> Unfortunately there's still an issue.
Ah, drat.
I'm just going to dump the c3tsc clocksource for now. If C3 mode is
available, the ACPI PM timer is available (since it is used for C3
timing), so we'll just fall back to ACPI PM if we see the cpu entering
C3 mode.
I'm working to respin a new release tonight, hopefully that will make it
upstream to -rt soon and that should take care of it. Later I can look
at reworking the c3tsc clocksource, but for now things need to just
work.
Thanks again for the testing and feedback, I really appreciate your
help!
-john
next prev parent reply other threads:[~2005-12-15 1:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 6:26 Jonathan Woithe
2005-12-05 19:42 ` john stultz
2005-12-07 3:39 ` Jonathan Woithe
2005-12-07 4:01 ` john stultz
2005-12-07 4:25 ` Jonathan Woithe
2005-12-07 22:54 ` Jonathan Woithe
2005-12-08 2:45 ` john stultz
2005-12-08 3:02 ` Jonathan Woithe
2005-12-08 3:22 ` john stultz
2005-12-08 4:11 ` Jonathan Woithe
2005-12-09 0:19 ` Jonathan Woithe
2005-12-09 2:11 ` john stultz
2005-12-09 2:19 ` Jonathan Woithe
2005-12-13 1:56 ` john stultz
2005-12-14 1:22 ` Jonathan Woithe
2005-12-15 1:41 ` john stultz [this message]
2005-12-15 3:18 ` Jonathan Woithe
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=1134610897.27117.4.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=jwoithe@physics.adelaide.edu.au \
--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
all inboxes | Powered by JetHome®