In result only the "omap" image is fully useful for profiling tasks (either with perf or Streamline). Also, I really wonder how the gator-module-* packages in the DS-5 PPA (https://launchpad.net/~linaro-maintainers/+archive/arm-ds5) build at all, as they need the above options being set...
And, generally, wouldn't it be a good idea to unify kernel configuration (I mean the non-platform-dependent bits) across LTs and Platforms builds? As we are heading in the direction of Single Kernel to Rule Them All, this will be needed at some point of time anyway.
The config files I've extracted from the debs and checked:
I just had a look at all the different kernels in https:/ /launchpad. net/~linaro- maintainers/ +archive/ kernel and the configurations are still very different:
HIGH_RES_TIMERS + + - + +
LOCAL_TIMERS N/A N/A + + +
PROFILING + - + + +
PERF_EVENTS + - - + -
HW_PERF_EVENTS + - + + -
FTRACE - - + + +
TRACING/
In result only the "omap" image is fully useful for profiling tasks (either with perf or Streamline). Also, I really wonder how the gator-module-* packages in the DS-5 PPA (https:/ /launchpad. net/~linaro- maintainers/ +archive/ arm-ds5) build at all, as they need the above options being set...
And, generally, wouldn't it be a good idea to unify kernel configuration (I mean the non-platform- dependent bits) across LTs and Platforms builds? As we are heading in the direction of Single Kernel to Rule Them All, this will be needed at some point of time anyway.
The config files I've extracted from the debs and checked:
config- 2.6.38- 1400-linaro- lt-mx5 3.0.0-1001- linaro- mx51 3.0.0-1001- linaro- vexpress 3.0.0-1007- linaro- omap 3.0.0-1402- linaro- lt-omap
config-
config-
config-
config-
$ grep CONFIG_ HIGH_RES_ TIMERS= y * 2.6.38- 1400-linaro- lt-mx5: CONFIG_ HIGH_RES_ TIMERS= y 3.0.0-1001- linaro- mx51:CONFIG_ HIGH_RES_ TIMERS= y 3.0.0-1007- linaro- omap:CONFIG_ HIGH_RES_ TIMERS= y 3.0.0-1402- linaro- lt-omap: CONFIG_ HIGH_RES_ TIMERS= y LOCAL_TIMERS= y * 3.0.0-1001- linaro- vexpress: CONFIG_ LOCAL_TIMERS= y 3.0.0-1007- linaro- omap:CONFIG_ LOCAL_TIMERS= y 3.0.0-1402- linaro- lt-omap: CONFIG_ LOCAL_TIMERS= y 2.6.38- 1400-linaro- lt-mx5: CONFIG_ PROFILING= y 3.0.0-1001- linaro- vexpress: CONFIG_ PROFILING= y 3.0.0-1007- linaro- omap:CONFIG_ PROFILING= y 3.0.0-1402- linaro- lt-omap: CONFIG_ PROFILING= y PERF_EVENTS= y * 2.6.38- 1400-linaro- lt-mx5: CONFIG_ PERF_EVENTS= y 3.0.0-1001- linaro- vexpress: CONFIG_ PERF_EVENTS= y 3.0.0-1007- linaro- omap:CONFIG_ PERF_EVENTS= y HW_PERF_ EVENTS= y * 2.6.38- 1400-linaro- lt-mx5: CONFIG_ HW_PERF_ EVENTS= y 3.0.0-1001- linaro- vexpress: CONFIG_ HW_PERF_ EVENTS= y 3.0.0-1007- linaro- omap:CONFIG_ HW_PERF_ EVENTS= y 3.0.0-1001- linaro- vexpress: CONFIG_ FTRACE= y 3.0.0-1007- linaro- omap:CONFIG_ FTRACE= y 3.0.0-1402- linaro- lt-omap: CONFIG_ FTRACE= y TRACING= y\|CONFIG_ GENERIC_ TRACER= y\)" * 3.0.0-1007- linaro- omap:CONFIG_ GENERIC_ TRACER= y 3.0.0-1007- linaro- omap:CONFIG_ TRACING= y 3.0.0-1402- linaro- lt-omap: CONFIG_ TRACING= y
config-
config-
config-
config-
$ grep CONFIG_
config-
config-
config-
$ grep CONFIG_PROFILING=y *
config-
config-
config-
config-
$ grep CONFIG_
config-
config-
config-
$ grep CONFIG_
config-
config-
config-
$ grep CONFIG_FTRACE=y *
config-
config-
config-
$ grep -e "\(CONFIG_
config-
config-
config-