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

[Xen-devel] question about timer_interrupt()

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] question about timer_interrupt()
From: Rik van Riel <riel@xxxxxxxxxx>
Date: Wed, 16 Nov 2005 13:52:34 -0500 (EST)
Delivery-date: Wed, 16 Nov 2005 18:52:44 +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
I have been reading through timer_interrupt() and related
functions for a bit now, and think I have found a potential
problem.

If a virtual CPU is preempted by the hypervisor while a
process is running on it, it looks like that unlucky
process will get "billed" for CPU time during which the
virtual CPU was not running ...

Am I overlooking something, or is it time to figure out
a way to separate virtual time from wall time so we can
account for the actual CPU time used by processes ?

>From what I can see, this might require a change to the
hypervisor interface, but I am not sure.  Ideas ?

-- 
All Rights Reversed

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] question about timer_interrupt(), Rik van Riel <=