From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ryan Harper Subject: Re: [PATCH] enforce dom0 cpus and balloon out memory Date: Fri, 29 Jul 2005 10:17:20 -0500 Message-ID: <20050729151720.GF8702@us.ibm.com> References: <9cde8bff05072820043a496e14@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <9cde8bff05072820043a496e14@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: aq Cc: Ian Pratt , xen-devel List-Id: xen-devel@lists.xenproject.org * aq [2005-07-29 09:01]: > This patch does 2 jobs: > > - Enforce the number of CPUs dom0 will take. See the new variable > "dom0-cpus" in xend-config.sxp (you will want to set this variable to > 1 on SMP systems) You could use vcpu-hotplug to drop the extra cpus from dom0 instead of writing directly into sysfs. The only stopper to that approach is the fact that dom0's self.channel is not initialized when xend starts and subsequently doesn't send the control message. Channels are initialized when a domain is built, but since dom0 is built by xen, the routine which sets up channels isn't called for dom0. Haven't found a good place for xend to initialized the channel for dom0 yet either. See vcpu_hotplug() in xen/xend/XendDomInfo.py Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx (512) 838-9253 T/L: 678-9253 ryanh@us.ibm.com