WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] profiling active RHEL 4 PV domains with xenoprof

To: "Santos, Jose Renato G" <joserenato.santos@xxxxxx>
Subject: Re: [Xen-devel] profiling active RHEL 4 PV domains with xenoprof
From: Andrew Evans <andrewe@xxxxxxxxxxxxx>
Date: Mon, 01 Feb 2010 10:40:26 -0800
Cc: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 01 Feb 2010 10:42:05 -0800
Domainkey-signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:content-type:content-transfer-encoding; b=Hq0/6e3wf5zP2zb/omQBigIyOiZLYiygIwhD2cS7HMbq8dCXHuhlZSQ+JY4a4MwG
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <EF547E542C520A4D858CFEF5B404D05360854D45A9@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4B623BED.6090603@xxxxxxxxxxxxx> <EF547E542C520A4D858CFEF5B404D05360854D3FBC@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4B637C3B.8070000@xxxxxxxxxxxxx> <EF547E542C520A4D858CFEF5B404D05360854D45A9@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100122 Thunderbird/3.0.1
On 01/31/10 13:20, Santos, Jose Renato G wrote:
> Also remember that the samples from a domU guest will not be reported
> in dom0. You need to run opreport in each guest to obtain their samples.

Thanks, that's what I was missing. I thought domU samples were
automagically propagated up to dom0 somehow, since the examples I've
seen didn't say anything about running opreport in domUs that have been
actively profiled.

thanks,

-Andrew


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

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