From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/4] ftrace: updates for tip
Date: Wed, 12 Nov 2008 22:28:58 +0100 [thread overview]
Message-ID: <20081112212858.GA25295@elte.hu> (raw)
In-Reply-To: <20081112212127.455979814@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
>
> Ingo,
>
> The following patches are in:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
>
> branch: tip/devel
>
>
> Steven Rostedt (4):
> trace: rename unlikely profiler to branch profiler
> ftrace: rename unlikely iter_ctrl to branch
> ftrace: add tracer called branch
> ftrace: rename trace_unlikely.c file
>
> ----
> arch/x86/kernel/vsyscall_64.c | 2 +-
> arch/x86/vdso/vclock_gettime.c | 2 +-
> include/asm-generic/vmlinux.lds.h | 2 +-
> include/linux/compiler.h | 19 ++-
> kernel/trace/Kconfig | 10 +-
> kernel/trace/Makefile | 7 +-
> kernel/trace/trace.c | 16 +-
> kernel/trace/trace.h | 34 ++--
> kernel/trace/trace_branch.c | 320 +++++++++++++++++++++++++++++++++++++
> kernel/trace/trace_selftest.c | 23 +++
> kernel/trace/trace_unlikely.c | 278 --------------------------------
> 11 files changed, 390 insertions(+), 323 deletions(-)
pulled, thanks Steve!
Ingo
next prev parent reply other threads:[~2008-11-12 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 21:21 [PATCH 0/4] ftrace: updates for tip Steven Rostedt
2008-11-12 21:21 ` [PATCH 1/4] trace: rename unlikely profiler to branch profiler Steven Rostedt
2008-11-12 21:21 ` [PATCH 2/4] ftrace: rename unlikely iter_ctrl to branch Steven Rostedt
2008-11-12 21:21 ` [PATCH 3/4] ftrace: add tracer called branch Steven Rostedt
2008-11-12 21:21 ` [PATCH 4/4] ftrace: rename trace_unlikely.c file Steven Rostedt
2008-11-12 21:28 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-06 6:53 [PATCH 0/4] ftrace: updates for tip Steven Rostedt
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=20081112212858.GA25295@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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.