lkml.org 
[lkml]   [2009]   [Sep]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [tip:tracing/core] tracing/bkl: Add bkl ftrace events
From
Date
On Fri, 2009-09-25 at 06:19 +0000, tip-bot for Frederic Weisbecker
wrote:
> Commit-ID: 96a2c464de07d7c72988db851c029b204fc59108

> +#if !defined(_TRACE_BKL_H) || defined(TRACE_HEADER_MULTI_READ)
> +#define _TRACE_BKL_H
> +
> +#include <linux/tracepoint.h>
> +
> +TRACE_EVENT(lock_kernel,
> +
> + TP_PROTO(const char *func, const char *file, int line),
> +
> + TP_ARGS(func, file, line),
> +
> + TP_STRUCT__entry(
> + __field( int, lock_depth )

FYI,

By your request I added this as a common field ;-)

With commit:

637e7e864103a7a68c1ce43ada27dfc25c0d113f

But since other utilities outside of ftrace may use this trace point, it
may be OK to keep the duplicate information in the kernel lock API trace
points.

-- Steve

> + __field_ext( const char *, func, FILTER_PTR_STRING )
> + __field_ext( const char *, file, FILTER_PTR_STRING )
> + __field( int, line )
> + ),
> +
> + TP_fast_assign(
> + /* We want to record the lock_depth after lock is acquired */
> + __entry->lock_depth = current->lock_depth + 1;
> + __entry->func = func;
> + __entry->file = file;
> + __entry->line = line;
> + ),
> +
> + TP_printk("depth: %d, %s:%d %s()", __entry->lock_depth,
> + __entry->file, __entry->line, __entry->func)
> +);
> +



\
 
 \ /
  Last update: 2009-09-26 12:09    [W:0.035 / U:20.828 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site