[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140226190140.590029589@goodmis.org>
Date: Wed, 26 Feb 2014 14:01:40 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: linux-kernel@...r.kernel.org
Cc: Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Subject: [RFA][PATCH 0/4] tracing: Request for acks on fixing tracepoint code
[ Request for Acks ]
Due to module tainting, we have tracepoints that silently do not work.
That will be solved another way. But the trace event infrastructure should
not be created for tainted modules. That is, the debugfs files should
not exist for them.
By moving the tracepoint module taint test into tracepoint.h, we can
reuse that same test when creating the module tracepoint events.
Note, I had to remove the tracepoint.h include from module.h as there
was nothing in module.h that required tracepoint.h, but this broke
a couple of event files (migrate.h and writeback.h) because they did
not include tracepoint.h, and were just lucky that it was included
by module.h.
Steven Rostedt (Red Hat) (4):
tracing: Fix event header writeback.h to include tracepoint.h
tracing: Fix event header migrate.h to include tracepoint.h
tracing/module: Remove include of tracepoint.h from module.h
tracing: Do not add event files for modules that fail tracepoints
----
include/linux/module.h | 1 -
include/linux/tracepoint.h | 7 +++++++
include/trace/events/migrate.h | 2 ++
include/trace/events/writeback.h | 1 +
kernel/trace/trace_events.c | 4 ++++
kernel/tracepoint.c | 2 +-
6 files changed, 23 insertions(+), 21 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/
Powered by blists - more mailing lists