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] [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add supp

To: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools)
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 17 Jun 2010 07:09:04 +0100
Cc: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, Kathy Hadley <Kathy.Hadley@xxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 16 Jun 2010 23:10:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C19AC64.7090001@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcsN2ktM3HZjvNI8RU+V9YgFoJkKdAACUr45
Thread-topic: [Xen-devel] [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools)
User-agent: Microsoft-Entourage/12.24.0.100205
On 17/06/2010 06:02, "Juergen Gross" <juergen.gross@xxxxxxxxxxxxxx> wrote:

>> Oh yes, that was the old behaviour. I took a hatchet to the
>> scheduler/cpupool interfaces a few weeks ago and now we should only
>> initialise the scheduler once, unless extra cpupools are manually created.
> 
> Keir, what do you think about creating an "idle-scheduler" for the cpus not in
> any cpupool? It would only schedule the idle vcpu and could be VERY minimal.
> This could reduce the complexity of moving cpus from and to cpupools.
> 
> I could try to setup a patch if you support this idea (I'm asking for your
> opinion before starting this, as I'm rather busy with other tasks).

What we have now is fine (which is, basically, cpupool0 and the 'no-cpupool'
schedulers are one and the same thing). I don't want yet another scheduler
thanks. ;-)

 -- Keir



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