From: Mathieu Desnoyers Add information about including marker.h in the documentation. Signed-off-by: Mathieu Desnoyers Signed-off-by: Andrew Morton --- Documentation/marker.txt | 10 +++++++--- 1 files changed, 7 insertions(+), 3 deletions(-) diff -puN Documentation/marker.txt~linux-kernel-markers-documentation-update-markerh Documentation/marker.txt --- a/Documentation/marker.txt~linux-kernel-markers-documentation-update-markerh +++ a/Documentation/marker.txt @@ -34,6 +34,12 @@ variable by address that would be later * Usage +In order to use the macro MARK, you should include linux/marker.h. + +#include + +Add, in your code : + MARK(subsystem_event, "%d %s %p[struct task_struct]", someint, somestring, current); Where : @@ -49,9 +55,6 @@ The expression %p[struct task_struct] is standard that could eventually be used for pointer type checking in sparse. The brackets contain the type to which the pointer refers. -In order to use the macro MARK, you should include linux/marker.h or -linux/kernel.h (which also includes linux/marker.h). - Connecting a function (probe) to a marker is done by providing a probe (function to call) for the specific marker through marker_set_probe(). It will automatically connect the function and enable the marker site. Removing a probe @@ -91,6 +94,7 @@ optimization can be disabled through men #include #include +#include #define SUBSYSTEM_EVENT_FORMAT "%d %s %p[struct task_struct]" void probe_subsystem_event(const char *format, ...) _