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] xc_domain_getfullinfo() gone

To: Andrew Theurer <habanero@xxxxxxxxxx>
Subject: Re: [Xen-devel] xc_domain_getfullinfo() gone
From: Kip Macy <kip.macy@xxxxxxxxx>
Date: Fri, 13 May 2005 07:45:03 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 13 May 2005 14:44:35 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XSFnGIzNPS+ggAoojBm7cLE5/DhQRybxdrAMzzkG2Y+pOz40f3KXztHG28mCTVoPm6qk+YwWRV+bMrwAadSysGLD8/oYVf1gDFZC248X1QwedxnAV5hpNnqLOApazoDi27d10MH1wJXkP2b8YLGD/OZ0JpnR1g60IutIrZI9TnQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4284BC79.70003@xxxxxxxxxx>
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>
References: <4284BC79.70003@xxxxxxxxxx>
Reply-to: Kip Macy <kip.macy@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
It is already there. It hasn't been exported to python as the main
purpose is to query register state. You're welcome to add it.


                        -Kip




On 5/13/05, Andrew Theurer <habanero@xxxxxxxxxx> wrote:
> I noticed this was gone from libxc.  Would there be any objection to
> adding xc_domain_get_vcpu_info?  I am interested in querying the
> cpu_time for each vcpu for a utility that does something like:
> 
> vm-stat
> 
> cpu[ util] domN-vcpuM[util]...domY-vcpuZ[util]
> ------------ --------------------------------------
> cpu0[075.4] dom0-vcpu0[000.3] dom1-vcpu1[075.1]
> cpu1[083.7] dom1-vcpu2[083.7]
> cpu2[069.2] dom1-vcpu3[069.2]
> cpu3[075.9] dom1-vcpu0[075.9]
>                                                     < time interval>
> cpu0[100.0] dom0-vcpu0[000.5] dom1-vcpu1[099.5]
> cpu1[099.8] dom1-vcpu2[099.8]
> cpu2[099.8] dom1-vcpu3[099.8]
> cpu3[099.8] dom1-vcpu0[099.8]
> 
> cpu0[100.0] dom0-vcpu0[000.3] dom1-vcpu1[099.7]
> cpu1[099.7] dom1-vcpu2[099.7]
> cpu2[099.7] dom1-vcpu3[099.7]
> cpu3[099.7] dom1-vcpu0[099.7]
> 
> cpu0[100.0] dom0-vcpu0[000.6] dom1-vcpu1[099.4]
> cpu1[099.7] dom1-vcpu2[099.7]
> cpu2[099.7] dom1-vcpu3[099.7]
> cpu3[101.4] dom1-vcpu0[101.4]
> 
> And while we're on this subject, I wanted to track, per phys cpu,
> exec_domain context switches, and store this as ctx_switches in
> schedule_data struct.  I believe tracking context switches would be a
> good stat to have, for example, to expose problems like high domU
> traffic networking on one cpu system.  Any objection to this or suggestions?
> 
> Thanks,
> 
> -Andrew
> 
> _______________________________________________
> 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

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