| 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: Thu, 15 Feb 2007 20:30:24 -0500 From: Jeff Muizelaar <jeff@...idigm.net> To: linux-kernel@...r.kernel.org Subject: Using sched_clock for mmio-trace I've built a tool with the goal of logging mmio writes and reads by device drivers. See http://nouveau.freedesktop.org/wiki/MmioTrace. I'd like to add support for recording a time stamp on each read and write. Unfortunately, I am not sure which clock api I should use. I had a look at blktrace and saw that it uses 'sched_clock()' for time stamps. However, this symbol is not exported to modules, and from what I've read it sounds like its use is discouraged. 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. -Jeff - 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