mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Mathieu Desnoyers <compudj@krystal.dyndns.org>,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	Li Zefan <lizf@cn.fujitsu.com>,
	Masami Hiramatsu <mhiramat@redhat.com>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 3/9 - v2][RFC] tracing: Remove per event trace	registering
Date: Fri, 07 May 2010 08:42:30 -0400	[thread overview]
Message-ID: <bddfebe8-61b9-4fb7-b7e5-5b0664f2b47c@email.android.com> (raw)
In-Reply-To: <20100507042025.GC8069@nowhere>

[-- Attachment #1: Type: text/plain, Size: 2453 bytes --]



"Frederic Weisbecker" <fweisbec@gmail.com> wrote:

>On Mon, May 03, 2010 at 11:40:48PM -0400, Steven Rostedt wrote:
>> From: Steven Rostedt <srostedt@redhat.com>
>> 
>> This patch removes the register functions of TRACE_EVENT() to enable
>> and disable tracepoints. The registering of a event is now down
>> directly in the trace_events.c file. The tracepoint_probe_register()
>> is now called directly.
>> 
>> The prototypes are no longer type checked, but this should not be
>> an issue since the tracepoints are created automatically by the
>> macros. If a prototype is incorrect in the TRACE_EVENT() macro, then
>> other macros will catch it.
>
>
>
>Agreed. Typechecking matters for human code but not in this context.
>Considering that the tracepoint and the probe are created by the same
>CPP code, bugs will be tracked down quickly and located to a single
>place.
>
>
>
>
>> 
>> The trace_event_class structure now holds the probes to be called
>> by the callbacks. This removes needing to have each event have
>> a separate pointer for the probe.
>> 
>> To handle kprobes and syscalls, since they register probes in a
>> different manner, a "reg" field is added to the ftrace_event_class
>> structure. If the "reg" field is assigned, then it will be called for
>> enabling and disabling of the probe for either ftrace or perf. To let
>> the reg function know what is happening, a new enum (trace_reg) is
>> created that has the type of control that is needed.
>> 
>> With this new rework, the 82 kernel events and 616 syscall events
>> has their footprint dramatically lowered:
>> 
>>    text	   data	    bss	    dec	    hex	filename
>> 5788186	1337252	9351592	16477030	 fb6b66	vmlinux.orig
>> 5792282	1333796	9351592	16477670	 fb6de6	vmlinux.class
>> 5793448	1333780	9351592	16478820	 fb7264	vmlinux.tracepoint
>> 5796926	1337748	9351592	16486266	 fb8f7a	vmlinux.data
>> 5774316	1306580	9351592	16432488	 fabd68	vmlinux.regs
>> 
>> The size went from 16477030 to 16432488, that's a total of 44K
>> in savings. With tracepoints being continuously added, this is
>> critical that the footprint becomes minimal.
>> 
>> v2: Changed the callback probes to pass void * and typecast the
>>     value within the function.
>> 
>> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
>
>
>
>Very nice!!
>
>Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
>

Thanks! 

-- Steve 


-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

  reply	other threads:[~2010-05-07 13:02 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04  3:40 [PATCH 0/9 - v2][RFC] tracing: Lowering the footprint of TRACE_EVENTs Steven Rostedt
2010-05-04  3:40 ` [PATCH 1/9 - v2][RFC] tracing: Create class struct for events Steven Rostedt
2010-05-07  4:21   ` Frederic Weisbecker
2010-05-04  3:40 ` [PATCH 2/9 - v2][RFC] tracing: Let tracepoints have data passed to tracepoint callbacks Steven Rostedt
2010-05-07  3:52   ` Frederic Weisbecker
2010-05-07 14:09     ` Steven Rostedt
2010-05-07 18:06       ` Frederic Weisbecker
2010-05-07 19:10         ` Steven Rostedt
2010-05-04  3:40 ` [PATCH 3/9 - v2][RFC] tracing: Remove per event trace registering Steven Rostedt
2010-05-07  4:20   ` Frederic Weisbecker
2010-05-07 12:42     ` Steven Rostedt [this message]
2010-05-07 14:54     ` Mathieu Desnoyers
2010-05-07 15:12       ` Steven Rostedt
2010-05-07 15:31         ` Mathieu Desnoyers
2010-05-07 15:43           ` Steven Rostedt
2010-05-07 18:01       ` Frederic Weisbecker
2010-05-07 19:08         ` Steven Rostedt
2010-05-07 20:03           ` Frederic Weisbecker
2010-05-07 20:58           ` Mathieu Desnoyers
2010-05-07  8:20   ` Li Zefan
2010-05-07 12:59     ` Steven Rostedt
2010-05-04  3:40 ` [PATCH 4/9 - v2][RFC] tracing: Move fields from event to class structure Steven Rostedt
2010-05-07  4:49   ` Frederic Weisbecker
2010-05-07 12:57     ` Steven Rostedt
2010-05-04  3:40 ` [PATCH 5/9 - v2][RFC] tracing: Move raw_init from events to class Steven Rostedt
2010-05-04  3:40 ` [PATCH 6/9 - v2][RFC] tracing: Allow events to share their print functions Steven Rostedt
2010-05-04  3:40 ` [PATCH 7/9 - v2][RFC] tracing: Move print functions into event class Steven Rostedt
2010-05-04  3:40 ` [PATCH 8/9 - v2][RFC] tracing: Remove duplicate id information in event structure Steven Rostedt
2010-05-04  3:40 ` [PATCH 9/9 - v2][RFC] tracing: Combine event filter_active and enable into single flags field 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=bddfebe8-61b9-4fb7-b7e5-5b0664f2b47c@email.android.com \
    --to=rostedt@goodmis.org \
    --cc=acme@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=compudj@krystal.dyndns.org \
    --cc=fweisbec@gmail.com \
    --cc=hch@lst.de \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mhiramat@redhat.com \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®