From: John Sigler <linux.kernel@free.fr>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-rt-users@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: High resolution timers on ACPI-less kernel
Date: Tue, 09 Oct 2007 11:39:08 +0200 [thread overview]
Message-ID: <470B4C3C.3000406@free.fr> (raw)
In-Reply-To: <alpine.LFD.0.9999.0710091117020.25146@localhost.localdomain>
Thomas Gleixner wrote:
> On Tue, 9 Oct 2007, John Sigler wrote:
>
>> I'm using a -rt kernel with high resolution timer support.
>> http://rt.wiki.kernel.org/index.php/Main_Page
>> Linux version 2.6.22.1-rt9 (root@venus) (gcc version 3.4.6) #1 PREEMPT RT Tue
>> Oct 9 10:02:45 CEST 2007
>>
>> I enabled high resolution timer support and disabled ACPI support.
>> ...
>> High resolution timers do not work in this configuration.
>
> Correct
>
>> Any idea why?
>
> Yes
>
>> # cat /sys/devices/system/clocksource/clocksource0/available_clocksource
>> tsc pit jiffies
>>
>> # cat /sys/devices/system/clocksource/clocksource0/current_clocksource
>> tsc
>>
>> My timestamp counter is good. Why do I need ACPI for hrt?
>
> We do not trust TSC at all. Never ever.
>
> The kernel refuses to switch to high resolution mode, when there is no
> reliable backup clock source available. ACPI enables the acpi_pm
> timer, which is a trusted clock source and is used by the kernel to
> verify the correctness of the TSC. You might try to enable HPET.
OK. I seem to remember that you had a patch to enable HPET on ICH4?
Is it still available somewhere?
Regards.
prev parent reply other threads:[~2007-10-09 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 9:06 High resolution timers on ACPI-less kernel John Sigler
2007-10-09 9:15 ` Alessio Igor Bogani
2007-10-09 9:28 ` John Sigler
2007-10-09 9:34 ` Thomas Gleixner
2007-10-09 10:35 ` John Sigler
2007-10-09 9:20 ` John Sigler
2007-10-09 9:22 ` Thomas Gleixner
2007-10-09 9:39 ` John Sigler [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=470B4C3C.3000406@free.fr \
--to=linux.kernel@free.fr \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-rt-users@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;
as well as URLs for NNTP newsgroup(s).