public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	Li Zefan <lizf@cn.fujitsu.com>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Zhaolei <zhaolei@cn.fujitsu.com>,
	Tom Zanussi <tzanussi@gmail.com>
Subject: Re: [PATCH 0/5] tracing/core: various fixes
Date: Tue, 26 May 2009 22:06:41 +0200	[thread overview]
Message-ID: <20090526200640.GD5969@nowhere> (raw)
In-Reply-To: <alpine.DEB.2.00.0905261542230.26705@gandalf.stny.rr.com>

On Tue, May 26, 2009 at 03:46:24PM -0400, Steven Rostedt wrote:
> 
> I'm just coming back off of a holiday.
> 
> 
> On Tue, 26 May 2009, Frederic Weisbecker wrote:
> 
> > Hi Ingo, Steven,
> > 
> > I've gathered various tracing fixes that were posted recently.
> > 
> > Note: the commit b11c53e12f94a46b50bccc7a1a953d7ca1d54a31
> > 	(ftrace: Add task_comm support for trace_event)
> >       looks good to me. This v3 solves the two following unhandled
> >       dependencies in v1:
> > 
> > ENABLE_EVENT_TRACING -> CONTEXT_SWITCH_TRACER
> > EVENT_TRACING -> CONTEXT_SWITCH_TRACER
> > 
> > The latter is tricky because CONTEXT_SWITCH_TRACER depends
> > on CONFIG_FTRACE (the tracers menu) from which EVENT_TRACING
> > is excluded. A build error can then occur if something selects
> > CONFIG_TRACING elsewhere.
> > 
> > The fix written by Zhaolei follows the {ENABLE_}EVENT_TRACING
> > view: we now have CONTEXT_SWITCH_TRACER and ENABLE_CONTEXT_SWITCH_TRACER.
> > 
> > The former is used by EVENT_TRACING to record cmdlines.
> > The latter selects CONTEXT_SWITCH_TRACER plus CONFIG_TRACING.
> > To sum up, ENABLE_CONTEXT_SWITCH_TRACER acts only as a "relay".
> 
> The sched_switch tracer is very light weight. Not sure we need to keep
> it separate.
> 
> Basically, when tracing is enabled, we should simply get the event tracer 
> and the sched_switch tracer for free. The configs get a bit tricky with 
> dependencies. I'll take a look at it.
> 
> -- Steve


So, should I zap these patches from the pull request?
Or do you think about a delta solution?

Thanks,
Frederic.

 
> > 
> > It looks good to me, tell me and Zhaolei if you have doubts
> > about it.
> > 
> > Thanks.
> > 
> > The following changes since commit 5537937696c55530447c20aa27daccb8d0d29b33:
> >   Ming Lei (1):
> >         ftrace: fix check for return value of register_module_notifier in event_trace_init
> > 
> > are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> > 	tracing/core
> > 
> > Lai Jiangshan (1):
> >       tracing: add trace_event_read_lock()
> > 
> > Li Zefan (1):
> >       tracing/events: change the type of __str_loc_item to unsigned short
> > 
> > Pekka Enberg (1):
> >       kmemtrace: fix kernel parameter documentation
> > 
> > Zhaolei (2):
> >       ftrace: Add task_comm support for trace_event
> >       ftrace: clean up of using ftrace_event_enable_disable()
> > 
> >  Documentation/kernel-parameters.txt |   10 --------
> >  include/trace/ftrace.h              |    2 +-
> >  kernel/trace/Kconfig                |    9 +++++-
> >  kernel/trace/trace.c                |    8 ++++++
> >  kernel/trace/trace_events.c         |   42 +++++++++++++---------------------
> >  kernel/trace/trace_output.c         |   25 +++++++++++++++-----
> >  kernel/trace/trace_output.h         |    2 +
> >  7 files changed, 52 insertions(+), 46 deletions(-)
> > 


  reply	other threads:[~2009-05-26 20:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26  2:04 [PATCH 0/5] tracing/core: various fixes Frederic Weisbecker
2009-05-26  2:04 ` [PATCH 1/5] tracing: add trace_event_read_lock() Frederic Weisbecker
2009-05-26  2:04 ` [PATCH 2/5] tracing/events: change the type of __str_loc_item to unsigned short Frederic Weisbecker
2009-05-26  2:04 ` [PATCH 3/5] kmemtrace: fix kernel parameter documentation Frederic Weisbecker
2009-05-26  2:04 ` [PATCH 4/5] ftrace: Add task_comm support for trace_event Frederic Weisbecker
2009-05-26  2:04 ` [PATCH 5/5] ftrace: clean up of using ftrace_event_enable_disable() Frederic Weisbecker
2009-05-26 18:55 ` [GIT PULL v2][PATCH 0/10] tracing/core: various fixes Frederic Weisbecker
2009-05-26 21:30   ` Steven Rostedt
2009-05-26 22:22     ` Frederic Weisbecker
2009-05-26 19:46 ` [PATCH 0/5] " Steven Rostedt
2009-05-26 20:06   ` Frederic Weisbecker [this message]
2009-05-26 21:10     ` 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=20090526200640.GD5969@nowhere \
    --to=fweisbec@gmail.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    --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