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
| ||
|
Date: Mon, 28 Aug 2006 15:41:35 -0700 From: john stultz <johnstul@...ibm.com> To: linux@...izon.com Cc: linux-kernel@...r.kernel.org, theotso@...ibm.com, zippel@...ux-m68k.org Subject: Re: Linux time code On Fri, 2006-08-25 at 20:17 -0400, linux@...izon.com wrote: > > Overall, I like your idea quite a bit. Might we look forward to a > > patch? :) > > Researching this has led me into that pit of madness, the i8254 > programmable interval timer specification. > > This is the original IBM PC timer (well, the version after the original > 8253), counting at 13125000/11 = 1193181.81... Hz, programmed to divide > by 11932 to generate a 100 Hz timer interrupt. If you want to be picky, > the options are With the new clocksource code, we can (currently just i386, but the architecture is generic and I'm working on the other arches) make use of continuous clocksources for accumulating time instead of having the deal with the problematic PIT (as well as the lost ticks issue). Maybe I'm missing what you're proposing, but I think "that pit of madness" can now be avoided. :) thanks -john - 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/
Powered by blists - more mailing lists