I figured out the problem.
Only I'm not sure if it's actually a bug or not. :)
It seems as if it's in the userspace oprofile tools.
I commented out the following from oprofile/daemon/opd_trans.c and it
works fine now.
/* FIXME: this logic is perhaps too harsh? */
if (trans->current->ignored || (trans->last && trans->last->ignored)) {
verbprintf(vmisc, "in the harsh logic\n");
goto out;
}
Maybe it's just too harsh for MIPS platforms? The same version of
oprofile worked fine on my x86 workstation.
Thanks,
Steve
Steve Lazaridis wrote:
Thats true,
But my problem is that timer mode isn't even working
Ralf Baechle wrote:
On Thu, Mar 16, 2006 at 09:22:11PM -0500, Steve Lazaridis wrote:
Has anyone successfully ran oprofile on an au1550?
If so, was it in BigEndian mode?
Are there any known issues with oprofile on au1xxx platforms?
Alchemy processors don't implement performance counters, so there are
by definition no issues ;-) That unfortunately means you're stuck
with timer mode.
Ralf
