public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wu Zhangjin <wuzhangjin@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	linux-mips@linux-mips.org, LKML <linux-kernel@vger.kernel.org>,
	Ralf Baechle <ralf@linux-mips.org>, Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Nicholas Mc Guire <der.herr@hofr.at>
Subject: Re: [PATCH] mips-specific ftrace support
Date: Thu, 28 May 2009 22:56:05 +0800	[thread overview]
Message-ID: <1243522565.5183.8.camel@falcon> (raw)
In-Reply-To: <alpine.LFD.2.00.0905281644210.3397@localhost.localdomain>

On Thu, 2009-05-28 at 16:45 +0200, Thomas Gleixner wrote:
> On Thu, 28 May 2009, Steven Rostedt wrote:
> > On Thu, 28 May 2009, wuzhangjin@gmail.com wrote:
> > Could you possibly break this patch up into porting the tracers one by 
> > one. That is:
> > 
> > First patch: make function tracing work.
> > Second patch: make dynamic tracing work.
> > Third patch: add Function graph tracing.
> > Forth patch: the time stamp updates
> > 
> > This would make things a lot easier to review, and if one of the changes 
> > breaks something, it will be easier to bisect.
> 
> > >  include/linux/clocksource.h    |    4 +-
> > >  kernel/sched_clock.c           |    2 +-
> > >  kernel/trace/ring_buffer.c     |    3 +-
> > >  kernel/trace/trace_clock.c     |    2 +-
> > >  scripts/Makefile.build         |    1 +
> > >  scripts/recordmcount.pl        |   31 +++-
> 
> The changes to these generic files need to be separate as well.
> 

Acked, will update it later.

thanks!
Wu Zhangjin


      parent reply	other threads:[~2009-05-28 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 21:19 [PATCH] mips-specific ftrace support wuzhangjin
2009-05-28 14:21 ` Steven Rostedt
2009-05-28 14:45   ` Thomas Gleixner
2009-05-28 14:48     ` Steven Rostedt
2009-05-28 14:56     ` Wu Zhangjin [this message]

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=1243522565.5183.8.camel@falcon \
    --to=wuzhangjin@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=der.herr@hofr.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mingo@elte.hu \
    --cc=ralf@linux-mips.org \
    --cc=rostedt@goodmis.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