From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ryan Harper Subject: Re: [PATCH] 2nd try: 2/2 VCPU creation and allocation Date: Wed, 12 Oct 2005 11:15:31 -0500 Message-ID: <20051012161531.GV17358@us.ibm.com> References: <20051010151651.GK17358@us.ibm.com> <20051010152821.GN17358@us.ibm.com> <3f428c67eaeb9dd543c246e55a156fd3@cl.cam.ac.uk> <20051010160538.GO17358@us.ibm.com> <20051010162354.GP17358@us.ibm.com> <20051011151656.GT17358@us.ibm.com> <8a1ee1a6fae5f2217438c742318c4d1a@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <8a1ee1a6fae5f2217438c742318c4d1a@cl.cam.ac.uk> 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-12 11:05]: > > On 11 Oct 2005, at 16:16, Ryan Harper wrote: > > >Allocation map. > > What does this patch buy us, given that we already support per-vcpu > maps? If I understand correctly, this adds a per-domain map, which > seems redundant to me. I guess not as much as it did before we had build-time vcpu creation. I can easily translate the allocation map in the configuration file into a set of pincpu ops before allocating domain memory and achieve the same effect as the patch does without the changes to the domain structure and pincpu dom0_op. I'll resend without the changes to xen. -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx (512) 838-9253 T/L: 678-9253 ryanh@us.ibm.com