K L
2010-Sep-07 14:49 UTC
[Xen-devel] Xenoprof cannot do profiling with active mode in domU
Sorry for duplicate messages.
I also read Renato''s thread
(http://lists.xensource.com/archives/html/xen-devel/2010-01/msg01215.html).
It seems that the problems have something to do with configuration.
But I patched oprofile-0.9.5.tar.gz with patch
oprofile-0.9.5-xen.patch and complied successfully. I have no idea
what the problem is.
When I type ''opcontrol -l'', I will see the following:
testvm02:~/oprofile-0.9.5# opcontrol -l
Using timer interrupt.
I can locate the code in ''ophelp.c''
line 405:
if (cpu_type == CPU_TIMER_INT) {
if (!check_events)
printf("Using timer interrupt.\n");
exit(EXIT_SUCCESS);
}
Any comments are greatly appreciated.
Best,
Jeff
---------- Forwarded message ----------
From: K L <intervalmg@gmail.com>
Date: Sun, Sep 5, 2010 at 10:45 PM
Subject: xenoprofile cannot run in active mode in domU
To: xen-devel@lists.xensource.com
Dear all,
I have enable xen-3.4.2 oprofile configuration and compiled the
oprofile-0.9.5.tar.gz with patch oprofile-0.9.5-xen.patch.
I ''scp'' the xen-syms kernel and the vmlinux kernel to domU. I
want to
start the mode with:
opcontrol --start --event=CPU_CLK_UNHALTED:1000000:1:1:1 --xen
xen-syms-3.4.2 --vmlinux=vmlinux
But it shows the result like:
testvm02:~# opcontrol --start --event=CPU_CLK_UNHALTED:1000000:1:1:1
--xen xen-syms-3.4.2 --vmlinux=vmlinux You cannot specify any
performance counter events
because OProfile is in timer mode.
I have read previous thread ''Xenoprof: getting Oprofile out of timer
mode?''(http://copilotco.com/mail-archives/xen.2006/msg12482.html). It
seems the problem has been fixed. But why I cannot run xenoprofile in
active mode in domU. Does it have something to do with apic?(I have
configured in /etc/xen/testvm02.cfg with lapic)
My machine is HP proliant. I can provide further information if needed.
Thanks,
Jeff
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel