From: Thomas Gleixner <tglx@linutronix.de>
To: Stas Sergeev <stsp@aknet.ru>
Cc: Daniel Walker <dwalker@mvista.com>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] make pit clocksource continuous
Date: Sun, 13 May 2007 16:54:53 +0200 [thread overview]
Message-ID: <1179068094.22481.248.camel@localhost.localdomain> (raw)
In-Reply-To: <4646D493.9000309@aknet.ru>
On Sun, 2007-05-13 at 13:04 +0400, Stas Sergeev wrote:
> Hello.
>
> Thomas Gleixner wrote:
> > The PIT can only be used as a clock source, when it is in periodic mode,
> > but it is never continuous. If we miss one PIT interrupt the time
> > keeping is hosed.
> OK, thank you and Daniel for the explanations
> about the flag, but now to the problem.
> Before hrtimer_switch_to_hres() is called,
> the check for timekeeping_is_continuous() is
> performed in tick_ckeck_oneshot_change(), and
> that check fails (by adding a flag I compel it
> to succeed).
It succeeds, but it does not work correctly, because your time keeping
is unreliable.
> With that check failing,
> hrtimer_switch_to_hres() is never called, and
> the hrtimers do not work. That's why I posted
> that patch, but what would be the right way
> of getting the hrtimers to work?
> /proc/timer_list lists only the pit timesource.
> If I enable lapic then it is also listed, yet
> it doesn't help at all.
You need either pm_timer or hpet in order to switch to highres /
dynticks. Are those enabled in the kernel config ?
tglx
next prev parent reply other threads:[~2007-05-13 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 23:18 Stas Sergeev
2007-05-12 23:38 ` Daniel Walker
2007-05-13 7:16 ` Thomas Gleixner
2007-05-13 9:04 ` Stas Sergeev
2007-05-13 14:54 ` Thomas Gleixner [this message]
2007-05-13 16:48 ` Stas Sergeev
2007-05-13 16:50 ` Thomas Gleixner
2007-05-13 17:23 ` Stas Sergeev
2007-05-13 17:36 ` Thomas Gleixner
2007-05-13 17:55 ` Matthieu CASTET
2007-05-13 18:17 ` Stas Sergeev
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=1179068094.22481.248.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stsp@aknet.ru \
/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
Powered by JetHome