[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] some questions about Xenoprof


  • To: weiming <zephyr.zhao@xxxxxxxxx>
  • From: Muhammad Atif <m_atif_s@xxxxxxxxx>
  • Date: Sun, 4 Jan 2009 21:37:31 -0800 (PST)
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Sun, 04 Jan 2009 21:38:17 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=PlkSIh3bvEBZ2KP0zicIYNBdMbeJzbe33YFfaeQAoyafGbA229sDhZumElrmg8wt6bDjPdSceyaD6xD7fbSYzotsbtIc1WjMI6TaCqhBlDFVskiLSslgWc7k59nBm7MfcK94IC8Tkgo5KdHY2GLYb9NZ4pLZ9ua9i1NoKWrp+gs=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Nope, you need to either tell xenoprof to do active profiling or passive oprofiling, else it will only do profiling for dom0

For active profile do something like this,

opcontrol --start-daemon --active-domains=3,4           #here 3,4 are domIDs which we need to profile.
This will start the daemon but profiling will not start......

Now go to domU's
opcontrol --start

Go to dom0,
opcontrol --start

go to domU
opcontrol --dump
opreport

This will give you domU profile.....


For passive domain profiling, you need to patch the oprofile userland code. I would recommend oprofile-0.9.3.
First download oprofile-0.9.3 and then patch it. The patch can be downloaded from http://xenoprof.sourceforge.net/


 
Best Regards,
Muhammad Atif
 
Best Regards,
Muhammad Atif



From: weiming <zephyr.zhao@xxxxxxxxx>
To: Niraj Tolia <ntolia@xxxxxxxxx>
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>; "Santos, Jose Renato G" <joserenato.santos@xxxxxx>
Sent: Monday, January 5, 2009 3:02:50 PM
Subject: Re: [Xen-devel] some questions about Xenoprof

Hi Niraj,

Thanks for letting me know the "--separate=cpu" option.

As regarding collecting system-wide events, is running the command "opcontrol --start --no-vmlinux --event=XXXX:YYYY:ZZZZ" on dom0 enough? I need host-level statistics, not just of dom0 itself.

Thanks!
zwm


On Sun, Jan 4, 2009 at 10:51 PM, Niraj Tolia <ntolia@xxxxxxxxx> wrote:
On Sun, Jan 4, 2009 at 7:32 PM, weiming <zephyr.zhao@xxxxxxxxx> wrote:
> Hi,
>
> I want to use Xenoprof to monitors some system-wide events (like L2 misses
> etc).
>
> 1. I'm using Xen 3.3. I guess I don't need to patch it as I find that a
> hypercall and some source codes related to xenoprof are already there. So I
> just downloaded the patch against oprofile. After that, when I run opcontrol
> --help, I found that "--xen" was listed as an option. So I think my
> installation should be OK.
>
> 2. I will run some workloads on domU. What I want to monitor is the
> system-wide event counts like L2_LINES_IN. What should I do? Is running
> "opcontrol --start --no-vmlinux --event=XXXX:YYYY:ZZZZ" on dom0 enough? Need
> I specify "--passive-domains" or "--active-domains" ?
>
> 3. I'm running the system on a muliti-core machine. Can Xenoprof list the
> event counters per core?


Not per physical core. However, from what I understand, xenoprof can
list the event counters per VCPU if you use the --separate=cpu option.
So, you could pin the VCPUs to cores if that is what you really want.

Second, the current version of xenoprof has a bug that prevents it
from correctly collecting per-VCPU info. Renato (cc-ed) should have a
patch to fix this though.

Cheers,
Niraj

--
Niraj Tolia, Researcher, HP Labs
http://www.hpl.hp.com/personal/Niraj_Tolia/


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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.