[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A6F9F51.4010107@garzik.org>
Date: Tue, 28 Jul 2009 21:01:05 -0400
From: Jeff Garzik <jeff@...zik.org>
To: mingo@...hat.com, hpa@...or.com, a.p.zijlstra@...llo.nl,
tglx@...utronix.de, mingo@...e.hu
CC: paulus@...ba.org, linux-kernel@...r.kernel.org,
rostedt@...dmis.org, linux-tip-commits@...r.kernel.org
Subject: Re: perf_counter: hook up the tracepoint events
Peter Zijlstra wrote:
> diff --git a/init/Kconfig b/init/Kconfig
> index 8a38443..761129a 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -945,6 +945,11 @@ config PERF_COUNTERS
>
> Say Y if unsure.
>
> +config EVENT_PROFILE
> + bool "Tracepoint profile sources"
> + depends on PERF_COUNTERS && EVENT_TRACER
> + default y
> +
> endmenu
Adding help text would be... helpful. :)
The net result in this case was the addition of a completely-unexplained
Kconfig option late in 2.6.31-rc.
Maybe the x86 maintainers could help see that they don't push
unexplained Kconfig options upstream -- particularly ones we are asked
to enable by default?
Jeff
--
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