linux-kernel - [for-next][PATCH 0/4] tracing: trace_puts() and faster trace

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: <20130310152752.848922120@goodmis.org>
Date:	Sun, 10 Mar 2013 11:27:52 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: [for-next][PATCH 0/4] tracing: trace_puts() and faster trace_printk()

I thought I was done with my ftrace 3.10 patches, but oh well. There's
a few more things that I want to do for 3.10.

I noticed that I used trace_printk() in my tracing_snapshot() in case
it was used incorrectly, but then I realized that those caused the
kernel to preallocate the trace_printk() context buffers all the time
(1 page per context [4 of them], and per cpu). This was not what I wanted.
Thus is started creating a special "internal to ftrace" use that
would not need the context buffers. I added a trace_puts() for this
and then realized that this would be nice for others to use as trace_printk(),
even when doing a trace_bprintk(), still requires a scan of the fmt
string when there are no arguments in use.

Then I thought it would be nice if the compiler just picked trace_puts()
when trace_printk() had no args. Thus, I pulled out my old macro wizard
robe, hat and wand and started playing again. And I came up with patch #2.
:-)

These 4 patches are specific for using ftrace by developers, as the
functions an not called anywhere and are only to be used when a developer
is debugging their code.

Enjoy,

-- Steve

Steven Rostedt (Red Hat) (4):
      tracing: Add trace_puts() for even faster trace_printk() tracing
      tracing: Optimize trace_printk() with one arg to use trace_puts()
      tracing: Add internal ftrace trace_puts() for ftrace to use
      tracing: Let tracing_snapshot() be used by modules but not NMI

----
 include/linux/kernel.h       |   64 +++++++++++++++++++++++++++-
 kernel/trace/trace.c         |   94 ++++++++++++++++++++++++++++++++++++++++--
 kernel/trace/trace.h         |   13 ++++++
 kernel/trace/trace_entries.h |   23 +++++++++--
 kernel/trace/trace_output.c  |   75 +++++++++++++++++++++++++++++++++
 kernel/trace/trace_output.h  |    2 +
 6 files changed, 261 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/