Subject: Re: [PATCH] Tracing: do export trace_set_clr_event
From: Steven Rostedt <rostedt@goodmis.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Christoph Hellwig <hch@infradead.org>,
        Yuanhan Liu <yuanhan.liu@linux.intel.com>,
        linux-kernel@vger.kernel.org, Frederic Weisbecker <fweisbec@gmail.com>,
        Ingo Molnar <mingo@redhat.com>
In-Reply-To: <5b55a1$ijitko@fmsmga002.fm.intel.com>
References: <1289196312-25323-1-git-send-email-yuanhan.liu@linux.intel.com>
	 <20101108095610.GA22592@infradead.org>
	 <5b55a1$ijitko@fmsmga002.fm.intel.com>
Content-Type: text/plain; charset="ISO-8859-15"
Date: Mon, 08 Nov 2010 09:02:14 -0500
Message-ID: <1289224934.12418.1.camel@gandalf.stny.rr.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 880
Lines: 20

On Mon, 2010-11-08 at 10:14 +0000, Chris Wilson wrote:

> The question then became how to enable register tracing upon module load?
> This was the simpler proposal, add a module parameter to enable the
> tracepoints - hence the exporting of this routine. The alternative that we
> are mulling over is whether it is possible for ftrace to parse a trace= on
> every module load to manipulate the tracepoints within that module.

I like the trace=on parameter much better. If that is set we could
enable the tracepoints of that module at load time. I really do not want
to export the function that was proposed in that patch.

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/