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] [PATCH 1/2] cpu steal time accounting

To: "Rik van Riel" <riel@xxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH 1/2] cpu steal time accounting
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Tue, 21 Feb 2006 22:06:13 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 21 Feb 2006 14:19:33 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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: AcY25nokPkXDQ1OnSbqK2sq0wxh6QwABVpAw
Thread-topic: [Xen-devel] [PATCH 1/2] cpu steal time accounting
>From: Rik van Riel [mailto:riel@xxxxxxxxxx]
>Sent: 2006年2月21日 20:56
>On Tue, 21 Feb 2006, Tian, Kevin wrote:
>> Why do you need to add a new VCPUOP while doing same thing as
>Because the dom0_ops only work for dom0 and reworking that
>function to allow non-privileged domains to get info just
>on themselves would end up being a way uglier patch.

See your point now. Since physical processor id is also exported in your patch, 
will it cause a trend to allow non-privileged domain to query more physical 
context information about domain itself? Like GETDOMAININFO, GETVCPUCONTEXT, 
etc. For example, guest may use gap info between max_pages and tot_pages to 
decide whether eagerly adding free pages as caches. It can also consider that 
info as an indicator of some type of tight resource contention. If it's the 
usage model, maybe we can consider move them out of dom0_ prefix and make it 


Xen-devel mailing list