RE: [Xen-devel] [PATCH] Xenoprof patches for xen-unstable

["Santos, Jose Renato G" <joserenato.santos@xxxxxx>]

>> -----Original Message-----
>> From: Andrew Theurer [mailto:habanero@xxxxxxxxxx] 
>> Sent: Tuesday, May 31, 2005 10:38 AM
>> To: Santos, Jose Renato G
>> Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx
>> Subject: Re: [Xen-devel] [PATCH] Xenoprof patches for xen-unstable
>> 
>> 
>> Santos, Jose Renato G wrote:
>> 
>> >  Andrew,
>> >
>> >  Could you please send me the commands you are using
>> >  to run oprofile?
>> >  
>> >
>> 
>> Sure, I use:
>> 
>> opcontrol --vmlinux=/boot/vmlinux-`uname -r` 
>> --xen=/boot/xen-unstable-syms opcontrol --init
>> 
>> opcontrol --start
>> 
>> <benchmark>
>> 
>> opcontrol --stop
>> 
>> opreport -l
>> 
>> 
>> **I changed opcontrol to echo XENIMAGE and XEN_RANGE to 
>> ~/.oprofile/daemonrc so they are picked up by oprofiled.
>> 
>> oprofiled cmd line looks like:
>> 
>> oprofiled --separate-lib=0 --separate-kernel=0 --spearate-thread=0 
>> --separate-thread=0 --spearate-cpu=0 
>> --events=GLOBAL_POWER_EVENTS:29:0:100000:1:1:1, 
>> --vmlinux=/boot/2.6.11-xen0-up --kernel-range=c01000000,c03ed2ae 
>> --xen-image=/boot/xen-unstable-syms --xen-range=c01000000,c03fc45e
>> 

  Andrew,

  I think your changes to opcontrol are not doing the
  right thing. Your --xen-range option to oprofiled
  is not correct. It overlaps with the kernel range. 
  Look at my version of the oprofiled cmd line:
  (see --xen-range values).

  oprofiled --separate-lib=0 --separate-kernel=0 
--separate-thread=0 --separate-cpu=0 
--events=GLOBAL_POWER_EVENTS:29:0:100000:1:1:1, 
--vmlinux=/boot/vmlinux-syms-2.6.11.10-xen0 
--kernel-range=c0100000,c0422e31 
--xen-image=/boot/xen-3.0-devel-syms 
--xen-range=ff100000,ff13c567

  That is probably the reason you are not seeing 
  any Xen samples

  Renato

    

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