[Xen-devel] Capturing hypervisor idle cycles with oprofile

["Harris, James R" <james.r.harris@xxxxxxxxx>]

Greetings,

I am using oprofile-0.9.3 and am trying to capture idle CPU cycles as part of my profile.  I am able to see both the hypervisor and domain0 in my profile, so I *think* I have oprofile configured correctly, but either I am missing something or this is not supported.

Oprofile configuration:
opcontrol --vmlinux=/boot/vmlinux-syms-2.6.18-xen --xen=/boot/xen-syms-3.1.0 --active-domains=0

GRUB:
title Xen
        root (hd0,0)
        kernel /xen-3.1.0.gz dom0_mem=2G idle=poll
        module /vmlinuz-2.6.18-xen root=/dev/sda2 ro idle=poll console=tty0
        module /initrd-2.6.18-xen.img

I have tried both xen-3.1.0 and xen-unstable.  I can see both xen and vmlinux symbols in my profile, but none of these include poll_idle (or anything equivalent).  I am using the stock oprofile-0.9.3 which was just released this week and contains the Xen support (previous versions required a Xen-specific patch on top of oprofile).

I assume that the hypervisor is responsible for halting the CPU - if so, is there a way to configure the hypervisor to poll instead of halt?  Or is there a different way to expose idle cycles to oprofile under Xen?

Regards,

Jim Harris

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel