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] RFC: cpu frequency scaling

To: Rik van Riel <riel@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] RFC: cpu frequency scaling
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 25 Oct 2006 21:47:11 +0100
Delivery-date: Wed, 25 Oct 2006 13:58:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <453FA718.7030105@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acb4dr5Z/QboWGRpEdurmwANk04WTA==
Thread-topic: [Xen-devel] RFC: cpu frequency scaling
User-agent: Microsoft-Entourage/11.2.5.060620
On 25/10/06 7:04 pm, "Rik van Riel" <riel@xxxxxxxxxx> wrote:

> These approaches both have their drawbacks.  One requires porting over
> a series of drivers from Linux to the hypervisor, maintaining two sets
> into the future.  The second could mess up some of the credit
> scheduler's balancing, and requires Linux modifications to poll the
> hypervisor for the CPU load...
> 
> Also, it would mean the end of running a 1 vcpu small dom0, which some
> people seem to like.
> 
> Which of these approaches would you prefer?

Frequency changes in dom0, please. The 'small dom0' issue is easily handled
-- create a driver domain to handle the frequency management. Or move the
potentially resource-intensive processes in dom0 out to a domU (amounts to
the same thing, really). It ought to take little enough resource that having
a VCPU per PCPU should not affect scheduling of more user-visible VMs.

We want to have the flexibility to implement cpufreq policy in a user-space
process anyway, so the feedback loop requires an interface to be punched
through between Xen and a cpufreq-managing guest.

 -- Keir



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

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