> Hmm, thinking about it a bit more, what do you trace events give us that
> the event based syscall tracer doesn't?
Yup. I think we need two tracepoint.
1) need to know userland argument.
-> syscall tracer
2) need to know actual vma change.
-> need to trace more low layer
As I said, if userland app have following code,
mmap(0x10000, PROT_READ|PROT_WRITE)
mmap(0x10000, PROT_NONE)
second mmap implicitly unmap firt mmap region and map another region.
so if we want to track munmap activity, syscall exiting point is not
so good place. we need to trace per-vma activity.
btw, perf_event_mmap() already take vma argument.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxxx For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>