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-cim

[Xen-cim] Removing pcpus from the scheduling pool

To: "Emmanuel Ackaouy" <ackaouy@xxxxxxxxx>
Subject: [Xen-cim] Removing pcpus from the scheduling pool
From: "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>
Date: Tue, 19 Dec 2006 10:01:57 -0500
Cc: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, xen-cim@xxxxxxxxxxxxxxxxxxx, Jim Fehlig <jfehlig@xxxxxxxxxx>
Delivery-date: Tue, 19 Dec 2006 07:03:41 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <0951ba397e5752bf7a54f5ecaf67ad4e@xxxxxxxxx>
List-help: <mailto:xen-cim-request@lists.xensource.com?subject=help>
List-id: xen-cim mailing list <xen-cim.lists.xensource.com>
List-post: <mailto:xen-cim@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccjXn4R5ruqZzR9Qr6ddPxBJlz8mgAHnBMg
Thread-topic: Removing pcpus from the scheduling pool
Emmanuel,

The Xen-CIM team has a requirement that we should be able to remove
PCPUs from the scheduling pool. I quote..
> * Support for ResourcePoolConfigurationService on some pool types, 
> e.g. ProcessorPool.This functionality will support for example 
> removing PCPUs from the pool and dedicate to management domain, thus 
> restricting set of PCPUs available for consumption by VMs.  Does xen
support 
> this?  Can we mask PCPUs such that they are not available to VMs?
End quote.

What needs to be done to add this functionality to the current
scheduler? 

Alternately, since you mentioned that vcpu-pinning is not-soft, is it
possible that if we ran a dummy VM that was pinned to the pcpus, we
could do something so we would not be preempted (that would keep those
pcpus from being released into the general scheduling pool)? Is that
even possible? Or would it be more complicated than merely patching the
scheduler and providing a path to doing it via xend?
> VCPU affinity should not be soft. By the time the set 
> affinity hypercall returns, the VCPU in question should be 
> running on a physical CPU set in its affinity mask.

Thanks
Raj

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

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