On 10/05/2011 10:29 PM, Robin Lee Powell wrote:
>
> #
> # (For a higher level overview, try: perf report --sort comm,dso)
> #
>
> How helpful is that? -_-
>
> I'm guessing I need --guestkallsyms= ; since they're all the same
> kernel I thought it'd figure it out. I'll redo.
OK, here's a "better" version.
# Events: 46K cycles
#
# Overhead Command Shared Object Symbol
# ........ ........ ....................... .......................
#
74.81% qemu-kvm [unknown] [u] 0x7fbdffd4c18a
This is in userspace, so it seems the guest wasn't completely stuck.
Try 'top -b' inside the guest to record what happens, let's see what
processes this is and go from there.
25.14% qemu-kvm [guest.kernel.kallsyms] [g] 0xffffffff811112f0
This doesn't resolve, please make sure the kernel-debuginfo package is
installed in the guest and use the guestmount option. (or you can
install it in the host, I think)
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
