From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ryan Harper Subject: Re: [PATCH] 0/2 VCPU creation and allocation Date: Mon, 10 Oct 2005 10:28:21 -0500 Message-ID: <20051010152821.GN17358@us.ibm.com> References: <20051010151651.GK17358@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org * Keir Fraser [2005-10-10 10:26]: > > On 10 Oct 2005, at 16:16, Ryan Harper wrote: > > >Also included is a new VCPUOP, > >VCPUOP_create, which handles all of the vcpu creation tasks and leaves > >initialization and unpausing to VCPUOP_initialize. > > I think two new Xen operations is one too many. > > Either we should take set_max_vcpus, and have that implicitly do the > work of VCPUOP_create, or we should take VCPUOP_create (callable only > by domain0) and have that implicitly increase max_vcpus for the subject > domain. OK. I'll re-work VCPUOP_create to be callable only by dom0 and auto-increment max_vcpus. -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx (512) 838-9253 T/L: 678-9253 ryanh@us.ibm.com