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] [day] [month] [year] [list]

Message-ID: <4647561E.7090702@aknet.ru>
Date:	Sun, 13 May 2007 22:17:02 +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.
I was confused as to where the above "not" applies.

> It does _NOT_ work without pm_timer or hpet
Thanks, now its clear enough. :)

> hrtimer_get_res() works, but I have no idea why you need hrtimers in
> your driver at all.
This is a pc-speaker PCM driver which needs a
18.5KHz periodic freq at least (the normal freq
is 37KHz).
I used the PIT and only PIT for it in the past,
but now with using hrtimers, the PIT is no
longer enough. This is a bit annoying, and
really, after I added the flag to pit_clocksource,
it just started to work, so I thought something
can be done in order for it to keep working with
PIT only. But if there is no way to do it with
hrtimers, then oh well.

-
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/