Re: [Xen-devel] RE: [PATCH] Xenoprof passive domain support fixes

["Ray Bryant" <raybry@xxxxxxxxxxxxxxxxx>]

Renato,

One thing I am still puzzled by in all of this is the following:  In the 
"opreport -x" output, I get entries for both pxen*-syms (which is a symbolic 
link to the xen-syms I supplied on the opreport command line) AND I get 
entries for xen-syms itself:

  samples|      %|
------------------
    76273 23.7270 papps2-syms
    73306 22.8040 pxen2-syms
    63550 19.7691 vmlinux
    43024 13.3839 libc-2.4.so
    24406  7.5922 xen-syms
    17278  5.3748 jbd
    12228  3.8039 ext3
     9845  3.0626 oprofiled
      395  0.1229 qemu-dm
<snip>

Why is that?  (I've been told the xen-syms samples are samples in the 
hypervisor due to dom0 activity, but I've been unable to verify this).

Additionally, I find that "opreport -lx" will report "no symbols" for 
papps*-syms:

samples  %        app name                 symbol name
76273    23.7738  papps2-syms              (no symbols)
19131     5.9630  pxen2-syms               l2e_rw_fault
17278     5.3854  jbd                      (no symbols)
12228     3.8114  ext3                     (no symbols)
11840     3.6905  libc-2.4.so              vfprintf
10256     3.1967  libc-2.4.so              _IO_file_xsputn@@GLIBC_2.2.5
8587      2.6765  xen-syms                 general_protection
7374      2.2984  pxen2-syms               vmx_asm_vmexit_handler
5212      1.6245  pxen2-syms               resync_all
5128      1.5984  xen-syms                 write_cr3
<snip>

unless I do an "ln -s /boot/vmlinux2-syms /boot/papps2-syms".  (It appears 
that opreport should be creating papps2-syms instead of vmlinux2-syms??)

Finally, I'm not convinced yet that the sample reports for the HVM guest 
(papps2-syms or pvmlinux2-syms, in this case) are correct.  I'm going to run 
some native and xen profile sessions using the same benchmark and see if I 
can correlate the results at all.

-- 
Ray Bryant
AMD Performance Labs                   Austin, Tx
512-602-0038 (o)                 512-507-7807 (c)



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