From: Ingo Molnar <mingo@elte.hu>
To: John <shill@free.fr>
Cc: linux-kernel@vger.kernel.org, tglx@timesys.com,
johnstul@us.ibm.com, akpm@osdl.org
Subject: Re: One-shot high-resolution POSIX timer periodically late
Date: Tue, 6 Feb 2007 13:37:16 +0100 [thread overview]
Message-ID: <20070206123716.GA8481@elte.hu> (raw)
In-Reply-To: <45C1BE5C.9050001@free.fr>
* John <shill@free.fr> wrote:
> > 2.6.18-rt7 is pretty old, do you see the problem in 2.6.20-rc6-rt5
> > too?
>
> Ingo, Thomas,
>
> I cannot reproduce in 2.6.20-rc6-rt6, but it is not strictly an
> apples-to-apples comparison because I get a tsc clocksource in
> 2.6.20-rc6-rt6, and an acpi_pm clocksource in 2.6.18.6-rt7.
that suggests that the TSC was not deemed reliable by the newer kernel -
which almost always means it's not realiable. I think the problems you
were seeing are consistent with TSC being non-monotonic - so the fix is
to not use the TSC - and the newer kernel does this automatically.
Ingo
next prev parent reply other threads:[~2007-02-06 12:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.4zD54Ie6Ozt0P4YqQSicS+XzXGw@ifi.uio.no>
[not found] ` <fa.G+/T32f2o1M3+YGLca/O8NaAQyY@ifi.uio.no>
[not found] ` <fa.6Ua8xjNfLKQEZZgDsoJgPMyww4g@ifi.uio.no>
[not found] ` <fa.yQlV+WU0TgrJTVqjopa01tgCnT0@ifi.uio.no>
[not found] ` <fa.ucVrLJ1Lh6FjdBHRglsIUc8/evk@ifi.uio.no>
[not found] ` <fa.Id9oufyELrVbe5Wb8SRakwC0V50@ifi.uio.no>
2007-02-01 10:18 ` One-shot high-resolution POSIX timer periodically late John
2007-02-06 12:37 ` Ingo Molnar [this message]
2007-02-07 10:13 ` John
2007-02-05 16:37 ` John
2007-02-06 7:31 ` Peter Zijlstra
2007-02-07 10:25 ` John
2007-02-08 17:32 ` Thomas Gleixner
2007-02-09 15:25 ` John
2007-02-09 16:21 ` Benedikt Spranger
2007-02-09 16:43 ` Thomas Gleixner
[not found] <fa.mtUvfgenNQkCc8835prYbwyiPQs@ifi.uio.no>
[not found] ` <fa.lwkMc548uRMcUjd9KZ2pC1DMKT4@ifi.uio.no>
[not found] ` <fa.dTtI0ctv1nu+tCWiK6jGPnrX69k@ifi.uio.no>
[not found] ` <fa.CMU3scpnLxfHVWRFPcmfRl2CjhA@ifi.uio.no>
2007-01-30 17:38 ` John
2007-01-30 20:25 ` Ingo Molnar
[not found] <fa.NwnlFyMPfa3XG6my3HKGWnCW3x4@ifi.uio.no>
[not found] ` <fa.Ji4GnAbBF2FR5JbSxvxn2haJZIk@ifi.uio.no>
2007-01-25 9:59 ` John
2007-01-25 22:19 ` john stultz
[not found] ` <fa.8TBiwbgs8B881k+3X+IlFjhqpLI@ifi.uio.no>
2007-01-25 12:03 ` John
[not found] <45B729AF.4030701@privacy.net>
2007-01-24 19:02 ` john stultz
2007-01-24 20:09 ` Ingo Molnar
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=20070206123716.GA8481@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shill@free.fr \
--cc=tglx@timesys.com \
/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