linux-kernel - Re: [RFC PATCH 0/5] x86_64: enable clockevents and dynticks

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: <20070331092339.GA2033@elte.hu>
Date:	Sat, 31 Mar 2007 11:23:39 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Chris Wright <chrisw@...s-sol.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	john stultz <johnstul@...ibm.com>, Andi Kleen <ak@...e.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/5] x86_64: enable clockevents and dynticks


* Chris Wright <chrisw@...s-sol.org> wrote:

> This series converts x86_64 timers to clockevents drivers and then 
> enables dynticks.  There's some minor cleanups along the way.  The 
> lapic broadcast mechanism is untested, I'm sure it still needs work, 
> there's still some cruft in lapic_setup_timer.
> 
> This is just for comments at this point, now that it's working on my 
> test box in both NO_HZ=n and NO_HZ=n configurations (typically using 
> hpet).

hm, neat - did you take a look at the x86_64 clockevents code that is in 
-rt and that has been there for a year or so and has been tested quite 
extensively?

	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/