This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/6457] Provide I/O traces for iogrind
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 25 Apr 2008 12:55:03 -0000
- Subject: [Bug tapsets/6457] Provide I/O traces for iogrind
- References: <20080425113103.6457.mark@klomp.org>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From fche at redhat dot com 2008-04-25 12:55 -------
> What I really need to see (beyond what strace can show (ie. all I/O relevant
> syscalls)) is first touches of memory mapped pages: both reads and writes.
Ah, this is why you needed to use valgrind.
I don't think we can do exactly that from systemtap yet, since that would
require active interference with process memory mappings. Maybe we need
a utrace extension & event source for just that -- "touched a page for
the first time". Until then, we can probably intercept the kernel's
response to these occurrences: a page fault, or a dirty page writeout.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=6457
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.