From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/4] Various fixes and enhancements for tracing
Date: Sun, 16 Nov 2008 05:51:52 +0100 [thread overview]
Message-ID: <491FA6E8.2010506@gmail.com> (raw)
This patchset applies on latest -tip (and normally against latest Steven's tracing tree).
_ tracing/ftrace: Fixes unexpected -EINVAL when longest tracer name is set
_ tracing/ftrace: Change the type of the init() callback
_ tracing/branch-tracer: Fix a trace recursion on branch tracer
_ tracing/function-return-tracer: Support for dynamic ftrace on function return tracer
The first and the third are bug fixes and the others are submitted for purposes on improvement for
tracing and the function return tracer.
Note that I kept the "return" name for the names used in the last patch because we haven't yet
decided what could be the better name. But once we find it, I will change the name of data structures
and functions used by this tracer.
next reply other threads:[~2008-11-16 4:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 4:51 Frederic Weisbecker [this message]
2008-11-16 6:58 ` [PATCH 0/4] Various fixes and enhancements for 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=491FA6E8.2010506@gmail.com \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox