linux-kernel - Re: [patch] make pit clocksource continuous

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 13 May 2007 21:23:01 +0400
From:	Stas Sergeev <stsp@...et.ru>
To:	tglx@...utronix.de
CC:	Linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: [patch] make pit clocksource continuous

Hello.

Thomas Gleixner wrote:
>> Does this mean that on even an older
>> boards (without acpi at all) the hrtimers
>> won't work?
> Not if PIT is the only clocksource available.
So you mean it can work without both the
pm_timer and hpet? Sorry for bothering you
too much, but I am trying to use the hrtimers
in my driver module, so I'd like to know all
the corner-cases.

How can I test that situation when the hrtimers
work only with PIT? Apparently disabling the
pm_timer and hpet in config doesn't help testing
it at all, since it simply refuses to work then.

Should I use hrtimer_get_res() to see if the
hrtimers are available, or is there any better way?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/