This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] xenoprof problem

To: "Xin Zhao" <zhaoxin@xxxxxxxxxxxxxx>, "Xen devel list" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] xenoprof problem
From: "Santos, Jose Renato G" <joserenato.santos@xxxxxx>
Date: Tue, 23 May 2006 09:24:44 -0700
Delivery-date: Tue, 23 May 2006 09:25:23 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4472A287.4090806@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZ+LMnrUYezf2uWQ5+XQ/J9kXtqRwAV5T8g
Thread-topic: [Xen-devel] xenoprof problem

XenOprofile does not support single domain profiling yet,
but only system wide profiling. That means that profiling
has to be controled by dom0. You will not be able to run
Oprofile from a domU without running oprofile in dom0.
You can find a more detailed description in:

Below is a typical sequence of commands to run Oprofile in
multiple domains:

A) Sequence of commands to start profiling:
     1) On the initiator domain (dom0)
         > opcontrol --reset
           (clear out any previous data of current session)
         > opcontrol --start-daemon
                     <events> <dom0 kernel and xen images specs> ...
           (start OProfile daemon and specify the set of active and
           passive domains in the session)

     2) On each active domain (domU to be profiled)
         > opcontrol --reset
         > opcontrol --start <events> <domU kernel and xen images specs>
         (indicates domain is ready to process performance events)
     3) On initiator
         > opcontrol --start
         (Multi-domain profiling session starts)
         (This is only successful if all active domains are ready)

 B) Sequence of commands to stop profiling
     -  On initiator domain:
         > opcontrol --stop


>> -----Original Message-----
>> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
>> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Xin Zhao
>> Sent: Monday, May 22, 2006 10:50 PM
>> To: Xen devel list
>> Subject: [Xen-devel] xenoprof problem
>> I am using xen-unstable with kernel 2.6.16. I enabled the 
>> auditd when compiling kernel. After compile and restart, I 
>> did "opcontrol --start" 
>> in DomU. But I got the error message as following:
>> ------------------------------
>> Using default event: GLOBAL_POWER_EVENTS:100000:1:1:1 Using 
>> 2.6+ OProfile kernel interface.
>> Failed to open profile device: Operation not permitted 
>> Couldn't start oprofiled.
>> Check the log file "/var/lib/oprofile/oprofiled.log" and 
>> kernel syslog
>> -------------------------------------------------
>> Does anyone have similar experience? Is this the right way 
>> to profiling the performance in xen systems?
>> Thanks in advance for your help!
>> Xin
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>