| 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
| ||
|
Message-ID: <p73k5yhg9az.fsf@bingen.suse.de> Date: 16 Feb 2007 21:02:44 +0100 From: Andi Kleen <andi@...stfloor.org> To: Jeff Muizelaar <jeff@...idigm.net> Cc: linux-kernel@...r.kernel.org Subject: Re: Using sched_clock for mmio-trace Jeff Muizelaar <jeff@...idigm.net> writes: > > The question is, what api should I be using? I need something that can > be called from inside interrupt handlers, and obviously the more > accurate and the lower the overhead the better. Use do_gettimeofday(). sched_clock() is not for general use and only for some very limited use cases and will give you unexpected results in several cases. There are a few cases where gtod is still a little slow, but these are being addressed. In many cases it is fast. In some hardware it stays slow, but there is not much that can be done about that because of the hardware design. It works fine from interrupt handlers and other strange contexts. -Andi - 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