[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] some questions about Xenoprof
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/ Muhammad Atif 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:
_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |