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>
Subject: [PATCH tip/perf/core 0/3] [GIT PULL][3.12] tracing/perf: Optimization for perf tracing
Date: Wed, 14 Aug 2013 22:01:04 -0400 [thread overview]
Message-ID: <20130815020104.813498803@goodmis.org> (raw)
Ingo,
These three patches from Oleg are more perf related, but they
are based on some of the updates that Oleg did that are in 3.11-rc5.
I based this work off of v3.11-rc5 as it seems that tip/perf/core is
still based on 3.11-rc1. You may want to merge Linus's 3.11-rc5 before
pulling this.
All the patches have been acked by Peter Zijlstra.
Please pull the latest tip/perf/core tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
tip/perf/core
Head SHA1: d027e6a9c83440bf1ca9e5503539d58d8e0914f1
Oleg Nesterov (3):
tracing/perf: Expand TRACE_EVENT(sched_stat_runtime)
tracing/perf: Reimplement TP_perf_assign() logic
tracing/perf: Avoid perf_trace_buf_*() in perf_trace_##call() when possible
----
include/trace/events/sched.h | 22 ++++++++--------------
include/trace/ftrace.h | 33 ++++++++++++++++++++-------------
2 files changed, 28 insertions(+), 27 deletions(-)
next reply other threads:[~2013-08-15 2:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 2:01 Steven Rostedt [this message]
2013-08-15 2:01 ` [PATCH tip/perf/core 1/3] tracing/perf: Expand TRACE_EVENT(sched_stat_runtime) Steven Rostedt
2013-08-15 2:01 ` [PATCH tip/perf/core 2/3] tracing/perf: Reimplement TP_perf_assign() logic Steven Rostedt
2013-08-15 2:01 ` [PATCH tip/perf/core 3/3] tracing/perf: Avoid perf_trace_buf_*() in perf_trace_##call() when possible Steven Rostedt
2013-08-15 8:01 ` [PATCH tip/perf/core 0/3] [GIT PULL][3.12] tracing/perf: Optimization for perf tracing Ingo Molnar
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=20130815020104.813498803@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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.