From: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
To: johnstul@us.ibm.com (john stultz)
Cc: jwoithe@physics.adelaide.edu.au (Jonathan Woithe),
linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-rt21: slow-running clock
Date: Thu, 15 Dec 2005 13:48:36 +1030 (CST) [thread overview]
Message-ID: <200512150318.jBF3Ia9B010880@auster.physics.adelaide.edu.au> (raw)
In-Reply-To: <1134610897.27117.4.camel@cog.beaverton.ibm.com> from "john stultz" at Dec 14, 2005 05:41:36 PM
Hi John
> > > On Fri, 2005-12-09 at 12:49 +1030, Jonathan Woithe wrote:
> > > > > 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.
Not a problem - I'll test this next release soon (perhaps via -rt) and
confirm that things "just work" for me. I'm happy to keep testing things -
if you do need further tests done for c3tsc in future drop me a line.
Regards
jonathan
prev parent reply other threads:[~2005-12-15 3:16 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
2005-12-15 3:18 ` Jonathan Woithe [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=200512150318.jBF3Ia9B010880@auster.physics.adelaide.edu.au \
--to=jwoithe@physics.adelaide.edu.au \
--cc=johnstul@us.ibm.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
all inboxes | Powered by JetHome®