public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@aknet.ru>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: [patch] make pit clocksource continuous
Date: Sun, 13 May 2007 03:18:52 +0400	[thread overview]
Message-ID: <46464B5C.2080302@aknet.ru> (raw)

[-- Attachment #1: Type: text/plain, Size: 445 bytes --]

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

Signed-off-by: Stas Sergeev <stsp@aknet.ru>
CC: Thomas Gleixner <tglx@linutronix.de>


[-- Attachment #2: pit_cont.diff --]
[-- Type: text/x-patch, Size: 331 bytes --]

--- linux-2.6.21/arch/i386/kernel/i8253.c	2007-05-12 11:29:23.000000000 +0400
+++ linux-2.6.21-xx/arch/i386/kernel/i8253.c	2007-05-13 02:19:57.000000000 +0400
@@ -193,6 +193,7 @@
 	.mask	= CLOCKSOURCE_MASK(32),
 	.mult	= 0,
 	.shift	= 20,
+	.flags  = CLOCK_SOURCE_IS_CONTINUOUS,
 };
 
 static int __init init_pit_clocksource(void)

             reply	other threads:[~2007-05-12 23:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-12 23:18 Stas Sergeev [this message]
2007-05-12 23:38 ` [patch] make pit clocksource continuous Daniel Walker
2007-05-13  7:16 ` Thomas Gleixner
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=46464B5C.2080302@aknet.ru \
    --to=stsp@aknet.ru \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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