From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [Patch] use full-size cpumask for vcpu-pin Date: Tue, 10 Aug 2010 15:27:54 +0100 Message-ID: References: <19553.24054.564316.142633@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <19553.24054.564316.142633@mariner.uk.xensource.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: Ian Jackson , Juergen Gross Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 10/08/2010 15:11, "Ian Jackson" wrote: > Juergen Gross writes ("[Xen-devel] [Patch] use full-size cpumask for > vcpu-pin"): >> The reason is the allocation of the cpumap for pinning: the size is only for >> the ACTUAL number of physical cpus in the system, not the possible number. >> The solution is to allocate a cpumap for up to NR_CPUS. > > Thanks for this patch. However, this doesn't seem to be even slightly > backwards-compatible, because it changes the layout of the physinfo > sysctl response. The domctl and sysctl hypercalls do not need to be backward compatible across major Xen releases. All other hypercalls absolutely do. -- Keir