Add trace points to mmap, munmap, and brk
in [Kernel]
|
From: KOSAKI Motohiro on 21 Jul 2010 09:40 > This patch adds trace points to mmap, munmap, and brk that will report > relevant addresses and sizes before each function exits successfully. > > Signed-off-by: Eric B Munson <emunson(a)mgebm.net> I don't think this is good idea. if you need syscall result, you should use syscall tracer. IOW, This tracepoint bring zero information. Please see perf_event_mmap() usage. Our kernel manage adress space by vm_area_struct. we need to trace it if we need to know what kernel does. Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Eric B Munson on 27 Jul 2010 07:10 On Wed, 21 Jul 2010, KOSAKI Motohiro wrote: > > This patch adds trace points to mmap, munmap, and brk that will report > > relevant addresses and sizes before each function exits successfully. > > > > Signed-off-by: Eric B Munson <emunson(a)mgebm.net> > > I don't think this is good idea. if you need syscall result, you should > use syscall tracer. IOW, This tracepoint bring zero information. > > Please see perf_event_mmap() usage. Our kernel manage adress space by > vm_area_struct. we need to trace it if we need to know what kernel does. > > Thanks. The syscall tracer does not give you the address and size of the mmaped areas so this does provide information above simply tracing the enter/exit points for each call. perf_event_mmap does provide the information for mmap calls. Originally I sent a patch to add a trace point to munmap and Peter Z asked for corresponding points in the mmap family. If the consensus is that the trace point in munmap is the only one that should be added I can resend that patch. -- Eric B Munson IBM Linux Technology Center ebmunson(a)us.ibm.com
From: KOSAKI Motohiro on 27 Jul 2010 07:20 > On Wed, 21 Jul 2010, KOSAKI Motohiro wrote: > > > > This patch adds trace points to mmap, munmap, and brk that will report > > > relevant addresses and sizes before each function exits successfully. > > > > > > Signed-off-by: Eric B Munson <emunson(a)mgebm.net> > > > > I don't think this is good idea. if you need syscall result, you should > > use syscall tracer. IOW, This tracepoint bring zero information. > > > > Please see perf_event_mmap() usage. Our kernel manage adress space by > > vm_area_struct. we need to trace it if we need to know what kernel does. > > > > Thanks. > > The syscall tracer does not give you the address and size of the mmaped areas > so this does provide information above simply tracing the enter/exit points > for each call. Why don't you fix this? > perf_event_mmap does provide the information for mmap calls. Originally I sent > a patch to add a trace point to munmap and Peter Z asked for corresponding points > in the mmap family. If the consensus is that the trace point in munmap is the > only one that should be added I can resend that patch. > > -- > Eric B Munson > IBM Linux Technology Center > ebmunson(a)us.ibm.com > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|
Pages: 1 Prev: [PATCH] mfd: Add WM8321 support Next: ext4 trace events cause NULL pointer dereferences |