When some hardware setups or architectures do not allow OProfile to use
performance counters, OProfile operates in timer mode.

But, from 2.6.11-rc1, we need to specify the module parameter "timer=1" to
work on timer interrupt mode.  Change things so that we detect the absence of
the high-resolution timer and fall back to timer-based profiling
automatically.

Furthermore we can easily get oops by reading /dev/oprofile/cpu_type.
Signed-off-by: Akinobu Mita <amgta@yacht.ocn.ne.jp>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>