|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] Xenoprof errors with Xen-unstable
Padma,
Ah! Try using the --active-domains=5 option on the same command you
start the daemon (--start-daemon). I had forgotten that we chose to make
the --active-domains option not persistent. That means opcontrol does
not remember --active-domains of previous runs(commands). The rationale
for doing that was to avoid problems for users that wanted to run
oprofile in dom0 after had run with multiple domains. It seemed awkard
to force a user to run opcontrol with the option "--active-domains=0" to
erase the value used in previous runs. So we decided to make this option
volatile (i.e. valid only for the command where it appears). I guess
this needs to be documented in the man pages ...
Please let me know if this fixes your problem
Renato
>> -----Original Message-----
>> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
>> Apparao, Padmashree K
>> Sent: Friday, May 26, 2006 2:38 PM
>> To: Markus Armbruster
>> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>> Subject: RE: [Xen-devel] Xenoprof errors with Xen-unstable
>>
>>
>> Here is the commands used in dom0
>>
>> /usr/local/bin/opcontrol --deinit
>> /usr/local/bin/opcontrol --reset
>> /usr/local/bin/opcontrol --active-domains=5
>> --event=GLOBAL_POWER_EVENTS:3000000:1:1:1
>> --event=INSTR_RETIRED:3000000:1:1:1
>>
>> /usr/local/bin/opcontrol --vmlinux=/boot/vmlinux-syms-2.6.16.13-xen
>> --xen=/boot/xen-syms-3.0-unstable --start-daemon
>>
>> Where xm list shows
>>
>> Name ID Mem(MiB) VCPUs State Time(s)
>> Domain-0 0 512 4 r----- 282.7
>> Guest1 5 256 1 -b---- 131.6
>>
>>
>> Thanks
>> - Padma
>>
>> -----Original Message-----
>> From: Markus Armbruster [mailto:armbru@xxxxxxxxxx]
>> Sent: Friday, May 26, 2006 1:59 PM
>> To: Apparao, Padmashree K
>> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>> Subject: Re: [Xen-devel] Xenoprof errors with Xen-unstable
>>
>> "Apparao, Padmashree K" <padmashree.k.apparao@xxxxxxxxx> writes:
>>
>> > The files under /dev/Oprofile contain nothing.
>> > Active_domains has nothing in it
>>
>> Looks like you didn't succeed in declaring your active
>> domains. How exactly did you specify --active-domains? You
>> did read and follow the user guide[*], didn't you?
>>
>> [*] http://xenoprof.sourceforge.net/xenoprof_2.0.txt
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|