From: Li Zefan <lizf@cn.fujitsu.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Chase Douglas <chase.douglas@canonical.com>,
Prasad <prasad@linux.vnet.ibm.com>,
Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
Soeren Sandmann <sandmann@daimi.au.dk>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Tracing configuration review
Date: Wed, 26 May 2010 15:20:16 +0800 [thread overview]
Message-ID: <4BFCCBB0.6040101@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTinuHB9gPLBZs_QsHqOm6Y5nR91P_gFlVBXa-ilJ@mail.gmail.com>
Pekka Enberg wrote:
> On Tue, May 25, 2010 at 11:13 PM, Frederic Weisbecker
> <fweisbec@gmail.com> wrote:
>>> # CONFIG_KMEMTRACE is not set (Kconfig says N if unsure)
>> Deprecated. We have the kmem trace event that are a full replacement now.
>> Pekka, Gabriel, can we remove it now?
>
> I don't think ftrace supports boot-time tracing which kmemtrace did.
We can do boot-time tracing by passing "trace_event=" kernel parameter.
By passing "ftrace=kmemtrace", kmemtrace can be started when
calling tracer_alloc_buffer(), which is an early_initcall.
While trace events are inititialized as a fs_initcall, it can
be modified to an early_initcall.
Furthermore, I noticed the discussion on perf persistent events, which
seems to enable perf trace at boot time, so I think perf-kmem can take
advantage of this and will be a full-replacement of kmemtrace soon ?
> That said, I was probably the only one actually using the feature so
> maybe we can just nuke kmemtrace at this point...
If you agree on removing kmemtrace now, I'll re-send the patch.
next prev parent reply other threads:[~2010-05-26 7:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 19:31 Tracing configuration review Chase Douglas
2010-05-25 19:46 ` Steven Rostedt
2010-05-25 19:58 ` Chase Douglas
2010-05-25 20:20 ` Frederic Weisbecker
2010-05-25 20:17 ` Frederic Weisbecker
2010-05-25 22:01 ` Steven Rostedt
2010-05-25 23:13 ` Frederic Weisbecker
2010-05-26 10:57 ` [Patch] tracing: remove boot tracer Américo Wang
2010-05-26 15:49 ` Frederic Weisbecker
2010-05-25 20:13 ` Tracing configuration review Frederic Weisbecker
2010-05-25 21:09 ` Chase Douglas
2010-05-25 23:06 ` Frederic Weisbecker
2010-05-27 11:20 ` K.Prasad
2010-05-27 22:15 ` Frederic Weisbecker
2010-06-08 17:35 ` Randy Dunlap
2010-06-08 22:00 ` Chase Douglas
2010-06-11 21:51 ` Randy Dunlap
2010-06-14 2:41 ` Chase Douglas
2010-05-26 6:19 ` Pekka Enberg
2010-05-26 7:20 ` Li Zefan [this message]
2010-05-26 7:44 ` Pekka Enberg
2010-05-26 8:42 ` Eduard - Gabriel Munteanu
2010-05-26 9:12 ` Li Zefan
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=4BFCCBB0.6040101@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=chase.douglas@canonical.com \
--cc=eduard.munteanu@linux360.ro \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=penberg@cs.helsinki.fi \
--cc=prasad@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=sandmann@daimi.au.dk \
/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.