linux-kernel - [PATCH 0/6] [GIT PULL] x86,ring_buffer,tracing: updates for tip

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:	Fri, 24 Apr 2009 00:30:05 -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>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: [PATCH 0/6] [GIT PULL] x86,ring_buffer,tracing: updates for tip


Ingo,

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

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


Chris Wright (1):
      x86: use native register access for native tlb flushing

Lai Jiangshan (1):
      ring_buffer: compressed event header

Steven Rostedt (4):
      tracing/wakeup: move access to wakeup_cpu into spinlock
      tracing: increase size of number of possible events
      tracing: add size checks for exported ftrace internal structures
      tracing: fix cut and paste macro error

----
 arch/x86/include/asm/tlbflush.h   |    8 ++--
 include/linux/ftrace_event.h      |    5 ++-
 include/linux/ring_buffer.h       |   16 ++++---
 include/trace/define_trace.h      |    8 ++--
 kernel/trace/ring_buffer.c        |   83 ++++++++++++++++++-------------------
 kernel/trace/trace_events.c       |    5 ++-
 kernel/trace/trace_export.c       |    4 ++
 kernel/trace/trace_output.c       |    2 +
 kernel/trace/trace_sched_wakeup.c |    6 +-
 9 files changed, 75 insertions(+), 62 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/