mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Stas Sergeev <stsp@aknet.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] make pit clocksource continuous
Date: Sun, 13 May 2007 09:16:51 +0200	[thread overview]
Message-ID: <1179040612.22481.237.camel@localhost.localdomain> (raw)
In-Reply-To: <46464B5C.2080302@aknet.ru>

On Sun, 2007-05-13 at 03:18 +0400, Stas Sergeev wrote:
> Hello.
> 
> Without the attached patch, I wasn't able
> to get the PIT to work as a clocksource for
> high-res timers.
> I don't know whether the patch is correct,
> but I tested it and it works.
> Can someone please tell me what exactly
> does this flag mean? google reveals nothing
> sensible to me, sorry...
> 
> ---
> Set CLOCK_SOURCE_IS_CONTINUOUS flag for the PIT clocksource

Ouch no. The PIT has no continuous counter, especially not when we use
the PIT to generate the next event interrupt with variable length
intervals. 

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.

	tglx



  parent reply	other threads:[~2007-05-13  7:13 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 [this message]
2007-05-13  9:04   ` Stas Sergeev
2007-05-13 14:54     ` Thomas Gleixner
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=1179040612.22481.237.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --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

all inboxes | Powered by JetHome®