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][RESUBMIT] don't schedule unplugged vcpus

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH][RESUBMIT] don't schedule unplugged vcpus
From: Ryan Harper <ryanh@xxxxxxxxxx>
Date: Wed, 8 Jun 2005 16:52:44 -0500
Cc: Ryan Harper <ryanh@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 08 Jun 2005 21:51:56 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D28213A@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D28213A@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6+20040907i
* Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> [2005-06-08 16:44]:
> > I've added in changes to DOM0_GETDOMINFO and 
> > DOM0_GETVCPUCONTEXT hypercalls.  dominfo now creates a 
> > vcpu_online_map bitmap which marks whether vcpus are up or 
> > down.  I didn't want to clobber either the total number of 
> > vcpus allocated to a domain (n_vcpu) nor the vcpu_to_cpu 
> > mapping since both are still valid whether the vcpu is being 
> > scheduled or not.
> 
> I don't see why we care about vcpus that are down. From the user's point
> of view they've gone for good -- it just happens that Xen hasn't freed
> the memory in anticipation of it being used again. What do you think?

I don't think the users care so much as I want tools to be able to
extract the current state of affairs for load balancing or other
operations that want to account for domain state.

> 
> I'd be inclined just to enter '-1' in the vcpu_to_cpu map. BTW: we could
> make it an s16 rather than s32 at the same time. I think 32,768 CPUs
> should keep be enough for anyone :-) 

Sure.  

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@xxxxxxxxxx

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