From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Ky Srinivasan" Subject: Re: VCPU affinity Date: Mon, 18 Dec 2006 10:14:09 -0700 Message-ID: <4586768D.E57C.0030.0@novell.com> References: <4586644F.E57C.0030.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com, Keir Fraser List-Id: xen-devel@lists.xenproject.org Kier, Looks like we may have a problem in our tool stack. If I pin the VCPUs from the command line, VCPUs stay bound to the specified physical processors. However, if the binding is specified in the VM config file, it does not work. Looks like we are not correctly handling the CPU affinity information. Will keep you posted once I learn more. Regards, K. Y >>> On Mon, Dec 18, 2006 at 11:05 AM, in message , Keir Fraser wrote: > VCPUs will run only on CPUs in their affinity mask. If you want to pin to a > particular CPU then specify an affinity mask with only that CPU contained in > it. > > -- Keir > > > On 18/12/06 15:56, "Ky Srinivasan" wrote: > >> What is the best way to pin VCPUs. It looks like the implementation of >> affinity currently is at best only "soft". >> >> Regards, >> >> K. Y >> >> >> _______________________________________________ >> Xen- devel mailing list >> Xen- devel@lists.xensource.com >> http://lists.xensource.com/xen- devel > > > _______________________________________________ > Xen- devel mailing list > Xen- devel@lists.xensource.com > http://lists.xensource.com/xen- devel