Linux Kernel Markers
The marker activation functions sits in kernel/marker.c. A hash table is used to keep track of the registered probes and armed markers, so the markers within a newly loaded module that should be active can be activated at module load time. marker_query has been removed. marker_get_first, marker_get_next and marker_release should be used as iterators on the markers. [akpm@linux-foundation.org: coding-style fixes] Signed-off-by:Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> Acked-by:
"Frank Ch. Eigler" <fche@redhat.com> Cc: Christoph Hellwig <hch@infradead.org> Cc: Rusty Russell <rusty@rustcorp.com.au> Cc: Mike Mason <mmlnx@us.ibm.com> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Linus Torvalds <torvalds@linux-foundation.org>
Showing
- include/asm-generic/vmlinux.lds.h 6 additions, 1 deletioninclude/asm-generic/vmlinux.lds.h
- include/linux/marker.h 130 additions, 0 deletionsinclude/linux/marker.h
- include/linux/module.h 12 additions, 0 deletionsinclude/linux/module.h
- kernel/Kconfig.instrumentation 6 additions, 0 deletionskernel/Kconfig.instrumentation
- kernel/Makefile 1 addition, 0 deletionskernel/Makefile
- kernel/marker.c 525 additions, 0 deletionskernel/marker.c
- kernel/module.c 30 additions, 0 deletionskernel/module.c
Loading
Please register or sign in to comment