wcohen at redhat.com
Tue Dec 18 12:03:48 EST 2007
M. Edward (Ed) Borasky wrote:
> I don't have my physical unit yet, but I too am interested in profiling
> and performance tuning. Unfortunately I have no Python tuning experience
> so I can't be of much help at the moment. I do have a "virtual ship2",
> running on a 2.2 GHz Athlon64 X2, but that of course is cheating. :)
> Oprofile is a bit tough to work with -- it makes you install a whole
> bunch of GUI libraries just to get at the low-level profiling stuff. And
> the kernel needs to be rebuilt with the right options -- I don't know if
> the OLPC kernel does so. So for now, I think you'll probably be better
> off with lower-level command-line tools.
Newer versions of OProfile RPM have the gui interface split out into a separate
RPM (oprofile-gui). This was done in Jun 2006.
However, you appear to be correct about the oprofile kernel.
$ grep OPROFILE config*
config-olpc-generic:# CONFIG_OPROFILE is not set
It looks like I didn't enter a tracs entry for oprofile to be enabled:
More information about the Devel