linux-kernel - Re: [PATCH] mips-specific ftrace support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 28 May 2009 16:45:37 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Steven Rostedt <rostedt@...dmis.org>
cc:	wuzhangjin@...il.com, linux-mips@...ux-mips.org,
	LKML <linux-kernel@...r.kernel.org>,
	Ralf Baechle <ralf@...ux-mips.org>,
	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Nicholas Mc Guire <der.herr@...r.at>, wuzj@...ote.com
Subject: Re: [PATCH] mips-specific ftrace support

On Thu, 28 May 2009, Steven Rostedt wrote:
> On Thu, 28 May 2009, wuzhangjin@...il.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.

Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/