WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [Patch] use full-size cpumask for vcpu-pin

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [Patch] use full-size cpumask for vcpu-pin
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 10 Aug 2010 15:27:54 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 10 Aug 2010 07:30:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19553.24054.564316.142633@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acs4le/ah3bsKnUBQvaUFMRZG/fhrAAAkhnj
Thread-topic: [Xen-devel] [Patch] use full-size cpumask for vcpu-pin
User-agent: Microsoft-Entourage/12.24.0.100205
On 10/08/2010 15:11, "Ian Jackson" <Ian.Jackson@xxxxxxxxxxxxx> 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



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel