On Tue, Jun 17, 2014 at 6:00 PM, Iñigo Muguruza <[email protected]> wrote: > Dear OpenRISC community, > > I write this mail to inform about an issue I have found when I analyzed the > outcome data coming from or1200 and mor1kx profiling. I am working in making > a OpenRISC tutorial to help people install and execute the diverse > open-soruce SoC tools. In this tutorial a profiling test for or1200/mor1kx > is made. Surprisingly, the results are really different, inducting to think > about a fault/bug. (results in the attached txts) > > In the mor1kx, _reset and or1k_dmu_disable routines, takes really a big > percentage of the execution, while in or1200 is does not happen the same. >
It shouldn't ever end up in or1k_dmmu_disable, so obviously stalling/unstalling mor1kx at some particular spot triggers a bug. I can reproduce it even manually by hitting ctrl-c + c in gdb repeatedly many times. I'll take a closer look what's happening. Stefan _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
