From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Frank Ch. Eigler" <fche@redhat.com>,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH v7 2/2] Tracepoint: register/unregister struct tracepoint
Date: Sat, 22 Mar 2014 02:34:59 +0000 (UTC) [thread overview]
Message-ID: <1566544544.8458.1395455699322.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <20140321154000.19939515@gandalf.local.home>
----- Original Message -----
> From: "Steven Rostedt" <rostedt@goodmis.org>
> To: "Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>
> Cc: linux-kernel@vger.kernel.org, "Ingo Molnar" <mingo@kernel.org>, "Frederic Weisbecker" <fweisbec@gmail.com>,
> "Andrew Morton" <akpm@linux-foundation.org>, "Frank Ch. Eigler" <fche@redhat.com>, "Johannes Berg"
> <johannes.berg@intel.com>
> Sent: Friday, March 21, 2014 3:40:00 PM
> Subject: Re: [PATCH v7 2/2] Tracepoint: register/unregister struct tracepoint
>
> On Fri, 21 Mar 2014 01:19:02 -0400
>
> > diff --git a/include/linux/ftrace_event.h b/include/linux/ftrace_event.h
> > index 4e4cc28..1592c1c 100644
> > --- a/include/linux/ftrace_event.h
> > +++ b/include/linux/ftrace_event.h
> > @@ -230,6 +230,7 @@ struct ftrace_event_call {
> > struct list_head list;
> > struct ftrace_event_class *class;
> > char *name;
> > + struct tracepoint *tp;
>
>
> This change right here just added 17K to the kernel (on a minimum config):
>
> text data bss dec hex filename
> 8425515 2018936 1302528 11746979 b33ea3 vmlinux.orig
> 8424914 2036472 1302528 11763914 b380ca vmlinux
>
> The two are redundant. Might as well remove .name and then
> use .tp->name for referencing the name of the event.
What should we do about:
kernel/trace/trace_export.c:
struct ftrace_event_call __used event_##call = { \
.name = #call, \
.event.type = etype, \
.class = &event_class_ftrace_##call, \
.print_fmt = print, \
.flags = TRACE_EVENT_FL_IGNORE_ENABLE | TRACE_EVENT_FL_USE_CALL_FILTER, \
};
when replacing the .name for a .tp->name, it is unclear what the
tracepoint structure should be (is there even one ?).
Thanks,
Mathieu
>
> -- Steve
>
>
> > struct trace_event event;
> > const char *print_fmt;
> > struct event_filter *filter;
>
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2014-03-22 2:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 5:19 [PATCH v7 0/2] Tracepoint API simplification/cleanup Mathieu Desnoyers
2014-03-21 5:19 ` [PATCH v7 1/2] Tracepoint cleanup: remove unused API functions Mathieu Desnoyers
2014-03-21 5:19 ` [PATCH v7 2/2] Tracepoint: register/unregister struct tracepoint Mathieu Desnoyers
2014-03-21 19:40 ` Steven Rostedt
2014-03-22 2:34 ` Mathieu Desnoyers [this message]
2014-03-21 20:02 ` Steven Rostedt
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=1566544544.8458.1395455699322.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=akpm@linux-foundation.org \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
/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