On Sun, Sep 28, 2008 at 8:57 PM, Bernie Innocenti <[EMAIL PROTECTED]> wrote: > Riccardo Lucchese wrote: >> >> I haven't tried to run oprofile on the xo yet (it is on my todo list). > > Be careful, there's a catch with jffs2: it does not support the writable > shared mmap that oprofiled needs. This leads to a confusing situation where > you get an empty report file without any error given. > > Refer to this (possibly outdated) documentation for an easy workaround: > http://wiki.laptop.org/go/Oprofile_setup > > >> If I remember well, ExaDoMoveOutPixmap (or a function with a similar >> name) and memcpy were always on top of sysprof profiles in rendering >> tests. > > One advantage of repeating the profile now would be comparing the absolute > times between different X servers and Fedora runtimes. > > Also, leaf functions tell us very little. memcpy() might be called from > many different places to do different things. oprofile also supports stack > traces, but for some reason I could never get them to work on the XO. One > clue is that oprofile cannot use the NMI interrupt on the XO and falls back > to using a software timer instead. Perhaps the stack tracing code doesn't > like that.
In that case, maybe sysprof is just enough (and much easier to set up). Regards, Tomeu _______________________________________________ Sugar mailing list [email protected] http://lists.laptop.org/listinfo/sugar
