| 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: 16 Feb 2007 11:30:56 -0500 From: fche@...hat.com (Frank Ch. Eigler) 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: > I've built a tool with the goal of logging mmio writes and reads by > device drivers. See http://nouveau.freedesktop.org/wiki/MmioTrace. FWIW, this is exactly a type of add-on trace patch that could be mooted by adoption of the ltt/systemtap "marker" facility. With it, you would not need so much code (e.g. no new user-space tools at all, reuse of common tracing buffer logic, permanently placed hooks) and would probably get more utility. > [...] The question is, what [timer] 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. We in systemtap land have the same problem, and so far made do with slightly postprocessed per-cpu TSC values. - FChE - 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