linux-kernel - [PATCH 0/3] ftrace: start stop infrastructure changes

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]

Date:	Wed, 05 Nov 2008 16:24:28 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [PATCH 0/3] ftrace: start stop infrastructure changes

[
 Note, I'm now trying to learn to use git. I am experimenting with
 using a combination of quilt and git. I set up a git repo at:

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

 This series is in the tip/devel branch.

 I'll put my changes in that branch and then send out the patches
 as I have always done. But the introduction will list the shortlog
 of the changes, then followed by the patches themselves.

 I do this by using git format-patch and then having quilt send
 out the queue that was produced.

 I plan on automating a lot of this, but for this run, it was
 done manually.

]

Ingo,

The following patches are in

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

  branch: tip/devel

Steven Rostedt (3):
      ftrace: add quick function trace stop
      ftrace: soft tracing stop and start
      ftrace: restructure tracing start/stop infrastructure

The first two should be fine, but the last one changed the infrastructure
a bit, and will need a bit of testing.

-- Steve

--
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/