[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTinuHB9gPLBZs_QsHqOm6Y5nR91P_gFlVBXa-ilJ@mail.gmail.com>
Date: Wed, 26 May 2010 09:19:37 +0300
From: Pekka Enberg <penberg@...helsinki.fi>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: Chase Douglas <chase.douglas@...onical.com>,
Prasad <prasad@...ux.vnet.ibm.com>,
Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>,
Soeren Sandmann <sandmann@...mi.au.dk>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: Tracing configuration review
On Tue, May 25, 2010 at 11:13 PM, Frederic Weisbecker
<fweisbec@...il.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.
That said, I was probably the only one actually using the feature so
maybe we can just nuke kmemtrace at this point...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists