linux-kernel - Re: [patch 00/46] High resolution timer / dynamic tick update

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

Message-ID: <20070124193822.GA28259@elte.hu>
Date:	Wed, 24 Jan 2007 20:38:22 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Daniel Walker <dwalker@...sta.com>
Cc:	tglx@...utronix.de, Andrew Morton <akpm@...l.org>,
	LKML <linux-kernel@...r.kernel.org>,
	John Stultz <johnstul@...ibm.com>,
	Arjan van de Veen <arjan@...radead.org>,
	Roman Zippel <zippel@...ux-m68k.org>
Subject: Re: [patch 00/46] High resolution timer / dynamic tick update


* Daniel Walker <dwalker@...sta.com> wrote:

> > you are also misunderstanding the change. While the TSC is the only 
> > unstable clocksource right now, the previous code tied the TSC to 
> > the >pm-timer< clocksource. This change makes it generic, hence the 
> > TSC can be verified by a hpet-only system (no pm-timer) as well. 
> > Systems without a pm-timer and with a TSC are quite common. So it 
> > solves a real problem.
> 
> Using my patch set a TSC specific watchdog could be created that isn't 
> tied a another specific clock. [...]

in other words: Thomas was right with his approach and your criticism 
against the generic code was unjustified. (I agree with the other points 
of Thomas as well, so i'm going with his patchset for now.)

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