linux-kernel - [patch 00/17] Tracepoints v4 for linux-next

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20080715222604.331269462@polymtl.ca>
Date:	Tue, 15 Jul 2008 18:26:04 -0400
From:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
To:	akpm@...ux-foundation.org, Ingo Molnar <mingo@...e.hu>,
	linux-kernel@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	Masami Hiramatsu <mhiramat@...hat.com>
Subject: [patch 00/17] Tracepoints v4 for linux-next

Hi,

Here is the newest release of the Tracepoints, following the feedback from Peter
Zijlstra. The main change is the creation of include/trace/ as a placeholder
from tracepoint headers.

The patchset applies over linux-next patch-v2.6.26-next-20080715 in this order :

#This a separate RCU update upon which the tracepoints depend
rcu-read-sched.patch

tracepoints.patch
tracepoints-documentation.patch
tracepoints-samples.patch

lttng-instrumentation-irq.patch
lttng-instrumentation-scheduler.patch
lttng-instrumentation-timer.patch
lttng-instrumentation-kernel.patch

lttng-instrumentation-filemap.patch
lttng-instrumentation-swap.patch
lttng-instrumentation-memory.patch
lttng-instrumentation-page.patch
lttng-instrumentation-hugetlb.patch

lttng-instrumentation-net.patch
lttng-instrumentation-ipv4.patch
lttng-instrumentation-ipv6.patch

ftrace-port-to-tracepoints.patch

Mathieu

-- 
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
--
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/