From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Zhaolei <zhaolei@cn.fujitsu.com>,
Tom Zanussi <tzanussi@gmail.com>, Li Zefan <lizf@cn.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] tracing/lockdep: turn lock->name into an array
Date: Tue, 14 Apr 2009 00:42:21 +0200 [thread overview]
Message-ID: <20090413224219.GK5977@nowhere> (raw)
In-Reply-To: <1239662166-13208-1-git-send-email-fweisbec@gmail.com>
On Tue, Apr 14, 2009 at 12:36:06AM +0200, Frederic Weisbecker wrote:
> Impact: allow filtering by lock name / fix module tracing
>
> Currently, the "lock acquired" event is traced using a TRACE_EVENT.
> But we can't use the char * type for the name without risking to
> dereference a freed pointer. A lock name can come from a module
> towards lockdep and it is risky to only store its address because we
> defer its name printing.
>
> That's why this patch uses a fixed array size and copy the name.
> Also it lets us filter the lock name because the event filtering
> doesn't handle the char pointers. Such support is not needed yet since
> the events don't use it for now because it is rarely easy to keep track
> of a string while we defer its output.
>
> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> ---
> include/trace/lockdep_event_types.h | 13 +++++++++++--
> 1 files changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/include/trace/lockdep_event_types.h b/include/trace/lockdep_event_types.h
> index 863f1e4..68f84f4 100644
> --- a/include/trace/lockdep_event_types.h
> +++ b/include/trace/lockdep_event_types.h
> @@ -32,18 +32,27 @@ TRACE_FORMAT(lock_contended,
> TP_FMT("%s", lock->name)
> );
>
> +#define LOCK_NAME_SIZE 25
This constant may look a bit weird.
I just started with the assumption that a full lock name
will rarely exceed this length.
If you agree with it, I will expand the conversion of lockdep
TRACE_FORMAT to TRACE_EVENTS with the same assumption.
So that we will be able to use filters with locks events.
Thanks.
> +
> +/*
> + * We might loose the name if it comes from a module
> + * so we keep a fixed array size of 25, enough for most
> + * usecases.
> + */
> +
> TRACE_EVENT(lock_acquired,
> TP_PROTO(struct lockdep_map *lock, unsigned long ip, s64 waittime),
>
> TP_ARGS(lock, ip, waittime),
>
> TP_STRUCT__entry(
> - __field(const char *, name)
> + __array(char, name, LOCK_NAME_SIZE)
> __field(unsigned long, wait_usec)
> __field(unsigned long, wait_nsec_rem)
> ),
> TP_fast_assign(
> - __entry->name = lock->name;
> + strncpy(__entry->name, lock->name, LOCK_NAME_SIZE - 1);
> + __entry->name[LOCK_NAME_SIZE - 1] = 0;
> __entry->wait_nsec_rem = do_div(waittime, NSEC_PER_USEC);
> __entry->wait_usec = (unsigned long) waittime;
> ),
> --
> 1.6.1
>
next prev parent reply other threads:[~2009-04-13 22:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 22:36 [PATCH] tracing/lockdep: turn lock->name into an array Frederic Weisbecker
2009-04-13 22:42 ` Frederic Weisbecker [this message]
2009-04-13 22:58 ` Ingo Molnar
2009-04-14 7:48 ` Peter Zijlstra
2009-04-14 10:27 ` Ingo Molnar
2009-04-14 21:22 ` Frederic Weisbecker
2009-04-13 23:01 ` Ingo Molnar
2009-04-14 0:24 ` Frederic Weisbecker
2009-04-14 6:35 ` KOSAKI Motohiro
2009-04-14 6:53 ` Ingo Molnar
2009-04-14 6:56 ` KOSAKI Motohiro
2009-04-14 7:20 ` Peter Zijlstra
2009-04-14 10:25 ` Ingo Molnar
2009-04-17 17:25 ` Jeremy Fitzhardinge
2009-04-17 17:27 ` Peter Zijlstra
2009-04-17 17:36 ` Steven Rostedt
2009-04-17 20:29 ` Frederic Weisbecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090413224219.GK5977@nowhere \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tzanussi@gmail.com \
--cc=zhaolei@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox