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 errors with Xen-unstable

To: "John Levon" <levon@xxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Xenoprof errors with Xen-unstable
From: "Santos, Jose Renato G" <joserenato.santos@xxxxxx>
Date: Fri, 26 May 2006 18:00:02 -0700
Cc: "Apparao, Padmashree K" <padmashree.k.apparao@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Markus Armbruster <armbru@xxxxxxxxxx>
Delivery-date: Fri, 26 May 2006 18:00:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060527004418.GB8702@xxxxxxxxxxxxxxxxxxxx>
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: AcaBJrazFlLykSTwSTmSRgEVdILpvAAAhXXA
Thread-topic: [Xen-devel] Xenoprof errors with Xen-unstable
I will work out a patch for that

>> -----Original Message-----
>> From: John Levon [mailto:levon@xxxxxxxxxxxxxxxxx] 
>> Sent: Friday, May 26, 2006 5:44 PM
>> To: Santos, Jose Renato G
>> Cc: Apparao, Padmashree K; Markus Armbruster; 
>> xen-devel@xxxxxxxxxxxxxxxxxxx
>> Subject: Re: [Xen-devel] Xenoprof errors with Xen-unstable
>> On Fri, May 26, 2006 at 03:10:46PM -0700, Santos, Jose 
>> Renato G wrote:
>> > 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 ...
>> We should make it error out unless --start or --start-daemon 
>> has been specified.
>> regards
>> john

Xen-devel mailing list