lkml.org 
[lkml]   [2008]   [Oct]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectMarkers in (non-module) kernel code?
From
Date

I've been playing with adding some markers into ext4 to see if they
could be useful in solving some problems along with Systemtap. It
appears, though, that as of 2.6.27-rc8, markers defined in code which is
compiled directly into the kernel (i.e., not as modules) don't show up
in Module.markers:

kvm_trace_entryexit arch/x86/kvm/kvm-intel %u %p %u %u %u %u %u %u
kvm_trace_handler arch/x86/kvm/kvm-intel %u %p %u %u %u %u %u %u
kvm_trace_entryexit arch/x86/kvm/kvm-amd %u %p %u %u %u %u %u %u
kvm_trace_handler arch/x86/kvm/kvm-amd %u %p %u %u %u %u %u %u

(Note the lack of any of the kernel_sched_* markers, and the markers I
added for ext4_* and jbd2_* are missing as wel.)

Systemtap apparently depends on in-kernel trace_mark being recorded in
Module.markers, and apparently it's been claimed that it used to be
there. Is this a bug in systemtap, or in how Module.markers is getting
built? And is there a file that contains the equivalent information
for markers located in non-modules code?

Thanks, regards,

- Ted



\
 
 \ /
  Last update: 2008-10-03 21:19    [W:0.132 / U:0.628 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site