From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758351AbZEOABa (ORCPT ); Thu, 14 May 2009 20:01:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754163AbZEOABV (ORCPT ); Thu, 14 May 2009 20:01:21 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.123]:59910 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753442AbZEOABV (ORCPT ); Thu, 14 May 2009 20:01:21 -0400 Date: Thu, 14 May 2009 20:01:20 -0400 (EDT) From: Steven Rostedt X-X-Sender: rostedt@gandalf.stny.rr.com To: Frederic Weisbecker cc: LKML , Christoph Hellwig , Ingo Molnar , Mathieu Desnoyers , Andrew Morton Subject: Re: [RFC] tracing: adding flags to events In-Reply-To: <20090514235846.GA8051@nowhere> Message-ID: References: <20090514203351.GA5969@nowhere> <20090514235846.GA8051@nowhere> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 15 May 2009, Frederic Weisbecker wrote: > On Thu, May 14, 2009 at 07:18:23PM -0400, Steven Rostedt wrote: > > > > + > > > > #undef TRACE_EVENT > > > > #define TRACE_EVENT(call, proto, args, tstruct, assign, print) \ > > > > enum print_line_t \ > > > > @@ -127,6 +132,7 @@ ftrace_raw_output_##call(struct trace_iterator *iter, int flags) \ > > > > struct trace_seq *s = &iter->seq; \ > > > > struct ftrace_raw_##call *field; \ > > > > struct trace_entry *entry; \ > > > > + struct trace_seq *p; \ > > > > int ret; \ > > > > \ > > > > entry = iter->ent; \ > > > > @@ -138,7 +144,9 @@ ftrace_raw_output_##call(struct trace_iterator *iter, int flags) \ > > > > \ > > > > field = (typeof(field))entry; \ > > > > \ > > > > + p = &get_cpu_var(ftrace_event_seq); \ > > > > ret = trace_seq_printf(s, #call ": " print); \ > > > > + put_cpu(); \ > > > > > > > > > > > > I don't understand the role of this per-cpu trace_seq variable. > > > It doesn't seem to be used. > > > > See it now? ;-) > > > Still not :-) > > I don't understand, it doesn't seem to be used. May be I'm too > much sleepy to understand... That's because you cut out an important detail ;-) > > +#define __print_flags(flag, x...) ftrace_print_flags_seq(p, flag, x) -- Steve