This seems to be related to a recently fixed bug.

Try using Xen 4.0 or latest unstable or apply the patch posted in:

http://lists.xensource.com/archives/html/xen-devel/2009-12/msg00709.html

Renato

---

From: 박은병 [mailto:peb1611@xxxxxxxxx]
Sent: Saturday, January 23, 2010 12:33 AM
To: Santos, Jose Renato G
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Is it possible that xenoprof active domain profiling using pvops jeremy's kernel

I tried to use same pvops kernel(jeremy's) for both dom0 and domU, and dullor's patch.

But, it does not work well.

dom0# opcontrol --start-daemon --event=L2_RQSTS:100000 --xen=/boot/xen-syms-3.4.2 --vmlinux=/boot/vmlinux-2.6.31.6-xen-xenoprof --active-domains=1
Using 2.6+ OProfile kernel interface.
Reading module info.
Using log file /var/lib/oprofile/samples/oprofiled.log
Daemon started.

dom0 seems to be good. I think,,

and domU command

domU# opcontrol --start --event=L2_RQSTS:100000 --xen=/boot/xen-syms-3.4.2 --vmlinux=/boot/vmlinux-2.6.31.6-domU-xenoprof
/usr/local/bin/opcontrol: line 367: timer: command not found
You cannot specify any performance counter events
because OProfile is in timer mode.

And. Some tricky output..

dom0#>cat /dev/oprofile/cpu_type

i386/core

domU#>cat /dev/oprofile/cpu_type

timer

I would appreciate your response....:)

2010년 1월 23일 오전 3:32, Santos, Jose Renato G <joserenato.santos@xxxxxx>님의 말:

To run xenoprof in active mode you need xenoprof support both in dom0 and in domU. Try using the the pvops kernel with Dullor's xenoprof patch in domU too. This should solve your problem...

Renato

---

From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of ???
Sent: Thursday, January 21, 2010 10:00 PM
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Is it possible that xenoprof active domain profiling using pvops jeremy's kernel

my system configuration

xen 3.4.2, oprofile 0.9.5( xenoprof patched ), dom0( jeremy's pvops kernel 2.6.31.6 - patched dullor's xenoprof patch ), domU( vanilla kernel 2.6.32 with paravirt enabled ), distribution( ubuntu 9.10 )

In passive mode, xenoprof seems to work well, opreport showed good information.

but, in active mode, it seems not to be done correctly.

my command is strictly followed by xenoprof tutorial doc.

<dom0>
opcontrol --start-daemon --event=L2_RQSTS:100000 --xen=/boot/xen-syms-3.4.2 --vmlinux=/boot/vmlinux-2.6.31.6-xen-xenoprof --active-domains=7

<domU>
opcontrol --start --event=L2_RQSTS:100000 --xen=/boot/xen-syms-3.4.2 --vmlinux=/boot/vmlinux-2.6.32-domU

In domU, opcontrol was break showing "cannot find timer command??"

I think that domU kernel also should be patched. Is it right?? dullor's patch available on vanilla kernel?? I had tried to patch the dullor's patch to vanilla kernel 2.6.31.6 with 2 conflict message.(mmu.c, xen-ops.h)

is there anyone who succeed in running xenoprof in active mode using jeremy's pvops 2.6.31.6 dom0 ??