From: Anton B. <an...@sa...> - 2005-04-29 13:30:12
|
Hi, > This is pretty odd. Maynard, is this some weird PPC64 thing? It would be > quite surprising to see 50% of the samples in op_model_power4.c, > especially the given line number. It /should/ be telling you > "power4_reg_setup" as the symbol. Can you do nm on the vmlinux and look > for that (then check it against opreport -wlg output) ? This issue highlights the current hacks we have on ppc64: - all unknown kernel ticks go to kernel_unknown_bucket. - all hypervisor ticks go to the hypervisor_bucket - all rtas ticks (rtas can be thought of as part of firmware) go to the rtas_bucket We can clean this up with a few changes: - Dont drop unknown samples. unknown_kernel_bucket was a quick hack to make sure we never lost samples. We should be doing that in the oprofile userspace instead. It would be nice to summarize these unknown user/kernel/hypervisor ticks separately. - Create a new state for hypervisor samples. We can then pass this data straight out to oprofile. - Keep the rtas_bucket. Its a pain to work out if a tick happened in RTAS and time spent there should be fairly low. So adding them all into this bucket sounds reasonable, its a ppc specific thing anyway. Anton |