linux-kernel - Re: [patch] sched: implement cpu_clock(cpu) high-speed time source, take #2

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]

Message-ID: <469F9178.7060801@goop.org>
Date:	Thu, 19 Jul 2007 09:29:44 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	stable@...nel.org, Greg KH <greg@...ah.com>,
	Chris Wright <chrisw@...s-sol.org>,
	Jens Axboe <jens.axboe@...cle.com>,
	Srivatsa Vaddagiri <vatsa@...ibm.com>,
	Jan Glauber <jang@...ux.vnet.ibm.com>, Andi Kleen <ak@...e.de>,
	Zachary Amsden <zach@...are.com>
Subject: Re: [patch] sched: implement cpu_clock(cpu) high-speed time source,
 take #2

Ingo Molnar wrote:
> that's still an important question, but these changes are still needed 
> nevertheless, to unbreak softlockup.c 

Well, I'm happy with using jiffies as the backport fix for softlockup
(if sched_clock is indeed a problem there), but mainly because it won't
affect Xen.  I don't know what effect it will have on vmi though.

cpu_clock seems like a good approach for .23 onwards.  I guess I should
test it at some point...

    J


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