linux-kernel - [PATCH 0/2][RFC] tracing: Showing symbols for 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: <20100212190907.954438555@goodmis.org>
Date:	Fri, 12 Feb 2010 14:09:07 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Mathieu Desnoyers <compudj@...stal.dyndns.org>,
	Lai Jiangshan <laijs@...fujitsu.com>,
	Li Zefan <lizf@...fujitsu.com>, Christoph Hellwig <hch@....de>,
	Wu Fengguang <fengguang.wu@...el.com>
Subject: [PATCH 0/2][RFC] tracing: Showing symbols for TRACE_EVENT

[Re-sending since my first try was missing a '>' from Frederic's
 email address, and it screwed up quilt mail ]

The __print_symbolic() macro is used by TRACE_EVENT TP_printk to convert
numbers into symbols. But if those numbers are defined as ENUMS, it works
fine for ftrace trace output, but a parser reading the binary trace
will not know how to translate the enum into a number.

The first patch creates a EXTRACT_TRACE_SYMBOL(sym) macro that
a <events>.h file can add to extract out all the enums that it uses
in TRACE_EVENTs. These symbols will then appear in the event_symbols
file in the events/ directory.

The second patch converts softirq symbols in include/trace/events/irq.h

This is an RFC patch set. I want to get your feedback before I push
this out of my git repo.

Thanks,

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