From mboxrd@z Thu Jan  1 00:00:00 1970
From: Zhigang Wang <zhigang.x.wang@oracle.com>
Subject: XenAPI: why we implement VM_metrics.VCPUs_utilisation
	as proportion?
Date: Wed, 03 Sep 2008 17:20:14 +0800
Message-ID: <48BE56CE.5060904@oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

hi all,

why we implement VM_metrics.VCPUs_utilisation as the proportion of all cpu time?

Then XenAPI client (xm) can not get the accumulated cpu_time of each vcpu.

I recommend we make VM_metrics.VCPUs_utilisation just the cpu_time which is
maintained by hypervisor.

Then XenAPI client (xm) not only can get the accumulated cpu_time of each vcpu,
but also can calculate the proportion by getting twice the
VM_metrics.VCPUs_utilisation.

Am I missing something?

thanks,

zhigang