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/
Home Products Support Community News


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

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [Patch] use full-size cpumask for vcpu-pin
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 13 Aug 2010 15:09:30 +0100
Cc: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 13 Aug 2010 07:11:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C88B078B.1DB63%keir.fraser@xxxxxxxxxxxxx>
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: Acs66P6ihsUYSx3hTHqLrb2bGAI6HQAAKSSBAAA3bqQAAB++rgAALXP1AAFb8WE=
Thread-topic: [Xen-devel] [Patch] use full-size cpumask for vcpu-pin
User-agent: Microsoft-Entourage/
On 13/08/2010 14:30, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx> wrote:

>> One suggestion: that we rename the syctl.physinfo field 'max_phys_cpus' to
>> 'max_possible_cpus'. The 'phys' is kind of redundant since this is the
>> physinfo sysctl, and 'possible' provides a better hint that this fields
>> indicates maximum possible supported CPUs now and forever on this boot of
>> the system.
> Even better, let's not introduce a new field at all, and let's always set
> sysctl.phys_info.max_cpu_id to NR_CPUS-1. Then I don't think any tools
> changes are needed.
> Yeah, that's what we should do. I will make a patch for that.

Done as xen-unstable:f6e1a597a92f. At this late stage it's probably a bit
too subtle for backport to 4.0.1 unfortunately (I hate to wonder if there
could be subtle side effects on xend's usage of these max_*_id fields).

 -- Keir

>  -- Keir
>>  -- Keir

Xen-devel mailing list