[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090507162849.GB5987@nowhere>
Date: Thu, 7 May 2009 18:28:50 +0200
From: Frederic Weisbecker <fweisbec@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
Li Zefan <lizf@...fujitsu.com>, Christoph Hellwig <hch@....de>
Subject: Re: [PATCH 7/7] tracing: add hierarchical enabling of events
On Wed, May 06, 2009 at 11:13:42PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt <srostedt@...hat.com>
>
> With the current event directory, you can only enable individual events.
> The file debugfs/tracing/set_event is used to be able to enable or
> disable several events at once. But that can still be awkward.
>
> This patch adds hierarchical enabling of events. That is, each directory
> in debugfs/tracing/events has an "enable" file. This file can enable
> or disable all events within the directory and below.
>
> # echo 1 > /debugfs/tracing/events/enable
>
> will enable all events.
>
> # echo 1 > /debugfs/tracing/events/sched/enable
>
> will enable all events in the sched subsystem.
>
> # echo 1 > /debugfs/tracing/events/enable
> # echo 0 > /debugfs/tracing/events/irq/enable
>
> will enable all events, but then disable just the irq subsystem events.
>
> When reading one of these enable files, there are four results:
>
> 0 - all events this file affects are disabled
> 1 - all events this file affects are enabled
> X - there is a mixture of events enabled and disabled
> ? - this file does not affect any event
Nice, I also planned to support hierarchical events but I'm too
slow, thanks!
--
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