From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: [RFA][PATCH 0/5] tracing: Ftrace error sync fix and tracepoint warn on failure
Date: Thu, 27 Feb 2014 10:46:16 -0500 [thread overview]
Message-ID: <20140227154616.703252665@goodmis.org> (raw)
This is a series of changes I plan on pushing for this release and
to stable. Feel free to ack (or nack, but I hope you don't ;-).
I pushed this up into my git repo as well, but it may change depending
on comments.
-- Steve
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
ftrace/urgent
Head SHA1: dd44790df744e71674558ae7ceb9dde3ed6f419c
Petr Mladek (1):
ftrace/x86: One more missing sync after fixup of function modification failure
Steven Rostedt (Red Hat) (4):
ftrace/x86: Run a sync after fixup on failure
tracing: Do not add event files for modules that fail tracepoints
tracepoint: Do not waste memory on mods with no tracepoints
tracepoint: Warn and notify if tracepoints are not loaded due to module taint
----
arch/x86/kernel/ftrace.c | 7 ++++---
include/linux/tracepoint.h | 6 ++++++
kernel/trace/trace_events.c | 4 ++++
kernel/tracepoint.c | 17 ++++++++++++++++-
4 files changed, 30 insertions(+), 4 deletions(-)
next reply other threads:[~2014-02-27 15:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 15:46 Steven Rostedt [this message]
2014-02-27 15:46 ` [RFA][PATCH 1/5] ftrace/x86: Run a sync after fixup on failure Steven Rostedt
2014-02-27 15:58 ` Petr Mládek
2014-02-27 16:02 ` Steven Rostedt
2014-03-03 22:12 ` H. Peter Anvin
2014-03-03 22:18 ` Steven Rostedt
2014-03-03 22:27 ` H. Peter Anvin
2014-03-03 22:31 ` Steven Rostedt
2014-02-27 15:46 ` [RFA][PATCH 2/5] ftrace/x86: One more missing sync after fixup of function modification failure Steven Rostedt
2014-02-27 16:05 ` Steven Rostedt
2014-02-27 16:37 ` Frederic Weisbecker
2014-02-27 17:00 ` Steven Rostedt
2014-02-27 17:19 ` Frederic Weisbecker
2014-02-27 17:35 ` Steven Rostedt
2014-02-27 17:52 ` Frederic Weisbecker
2014-02-27 15:46 ` [RFA][PATCH 3/5] tracing: Do not add event files for modules that fail tracepoints Steven Rostedt
2014-02-27 16:31 ` Mathieu Desnoyers
2014-02-27 15:46 ` [RFA][PATCH 4/5] tracepoint: Do not waste memory on mods with no tracepoints Steven Rostedt
2014-02-27 15:46 ` [RFA][PATCH 5/5] tracepoint: Warn and notify if tracepoints are not loaded due to module taint Steven Rostedt
2014-02-27 16:33 ` Mathieu Desnoyers
2014-02-27 17:06 ` Steven Rostedt
2014-02-27 17:09 ` Steven Rostedt
2014-02-27 17:16 ` Mathieu Desnoyers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140227154616.703252665@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.