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 02:24:04 +0200 [thread overview]
Message-ID: <20090414002403.GM5977@nowhere> (raw)
In-Reply-To: <20090413230110.GB817@elte.hu>
On Tue, Apr 14, 2009 at 01:01:10AM +0200, Ingo Molnar wrote:
>
> * Frederic Weisbecker <fweisbec@gmail.com> wrote:
>
> > TP_STRUCT__entry(
> > - __field(const char *, name)
> > + __array(char, name, LOCK_NAME_SIZE)
> > __field(unsigned long, wait_usec)
> > __field(unsigned long, wait_nsec_rem)
> > ),
>
> Hm. These constants tend to grow - 25 will certainly be too narrow.
> But increasing it increases the record size as well.
Yeah, that's why I'm not sure about the right size.
> I think we'll need an embedded __string() type, with a length field
> (but still also zero-delimited, for convenience), hm?
Indeed. It tends to be a repetitive pattern.
Also, may be we can use an undefined array size on the structure
for the __string field.
We already do so with the old style trace_printk entry and may be
some others. Extending TRACE_EVENT to support it shouldn't be a big deal.
I'll just wait for Steven changes and try to do that.
> Ingo
next prev parent reply other threads:[~2009-04-14 0:24 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
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 [this message]
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=20090414002403.GM5977@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