linux-kernel - [PATCH 0/3] [GIT PULL] updates for tip/tracing/ftrace

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-next>] [day] [month] [year] [list]

Message-Id: <20090324135422.026619569@goodmis.org>
Date:	Tue, 24 Mar 2009 09:54:22 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: [PATCH 0/3] [GIT PULL] updates for tip/tracing/ftrace


Ingo,

I rebased off of your latest tree. I'm still making some updates to the
function profiler. In doing so, I came across some changes that need to
be made in the function graph tracer. To keep those changes separate
from the function profiler, I'm posting these first.

Please pull the latest tip/tracing/ftrace tree, which can be found at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
tip/tracing/ftrace


Steven Rostedt (3):
      function-graph: moved the timestamp from arch to generic code
      function-graph: prevent more than one tracer registering
      function-graph: ignore times across schedule

----
 arch/x86/kernel/ftrace.c             |    6 +----
 include/linux/ftrace.h               |    3 +-
 include/linux/sched.h                |    2 +
 kernel/trace/ftrace.c                |   42 ++++++++++++++++++++++++++++++++++
 kernel/trace/trace_functions_graph.c |    8 ++++--
 5 files changed, 51 insertions(+), 10 deletions(-)
-- 
--
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/