Thread (11 messages) 11 messages, 6 authors, 2011-12-05

Re: oprofile callgraph support missing for common cpus

From: Andy Fleming <hidden>
Date: 2011-11-17 17:52:06

On Nov 17, 2011, at 11:30 AM, Maynard Johnson wrote:
quoted
=20
Notice the first
		 if (!cur_cpu_spec->oprofile_cpu_type)
		 		 return -ENODEV;
=20
		 if (firmware_has_feature(FW_FEATURE_ISERIES))
		 		 return -ENODEV;
For my e300c2 cpu both if's are false and I don't get support for =
callgraph/backtrace
quoted
support. Moving the ops->backtrace =3D op_powerpc_backtrace; to the =
top
quoted
enables backtrace for me.
What kernel version are you using?  Actually, looking at a 3.0.3 tree =
I happen to have available, I see oprofile h/w event support (in =
arch/powerpc/kernel/cputable.c) for e300c3 and e300c4, but not the other =
e300 flavors.  I've added Andy Flemming from Freescale to cc.  Maybe he =
knows why e300c2 isn't supported.

e300c2 does not have hardware performance monitor events.

However, it should be able to support timer-based profiling, right? And =
why not support backtrace from there? Do we require hardware counters to =
get a backtrace?

Andy
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help