From owner-freebsd-current@FreeBSD.ORG  Fri May 30 16:09:47 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 2D6EBB80;
 Fri, 30 May 2014 16:09:47 +0000 (UTC)
Received: from mail-qg0-x22d.google.com (mail-qg0-x22d.google.com
 [IPv6:2607:f8b0:400d:c04::22d])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id AEFE1257B;
 Fri, 30 May 2014 16:09:46 +0000 (UTC)
Received: by mail-qg0-f45.google.com with SMTP id z60so5940649qgd.32
 for <multiple recipients>; Fri, 30 May 2014 09:09:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:cc:content-type;
 bh=Px3gOiiqEhsJk+Kel1eG3zbTm8kUFmESPk0Q92+32Xc=;
 b=e5xiEvgP4DhcFVuLixcatMgwZZiYW1z0E8rAQ+RW70uPITJs1O/Ora6dL6At6FpgN2
 EKcXhhWyQKz0ddGAgnpUhzNKnTjQuhcL2NxJnKrvQOxbh/cYpFA4UZ0nExKnEwLWTnam
 5cr8LusdRsC+8jj+g33aNqEOxQcfcoW7gfq/zHYO5+rq0f3KAASsX5kRfDe0/vlAbZ0v
 BmUH3sV8EqCZlSlE/2NpRQH+C5XaG8bMMTJ8Wtj4kC3EVwsBUJDaehbXz3j41M/xOvnY
 jR+cfajgzmRWlvITV2/HW5EE91+ZuOxnxG2usimxEb6z+IN+B5hnYvf5cvLrJVaG4fsp
 6tag==
MIME-Version: 1.0
X-Received: by 10.140.22.209 with SMTP id 75mr21313043qgn.4.1401466185847;
 Fri, 30 May 2014 09:09:45 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.224.191.201 with HTTP; Fri, 30 May 2014 09:09:45 -0700 (PDT)
In-Reply-To: <201405301057.23736.jhb@freebsd.org>
References: <CAJ-VmonhjQZGhxTjgJA5a3Cyu+x7HCmuK1MDoLQtdpHJ4wR-FA@mail.gmail.com>
 <201405291729.33471.jhb@freebsd.org>
 <CAJ-Vmom5OBvj8b48SBgYpmK0u0E4+s7ar4E_YmjVifnHAeBhEw@mail.gmail.com>
 <201405301057.23736.jhb@freebsd.org>
Date: Fri, 30 May 2014 09:09:45 -0700
X-Google-Sender-Auth: rPqJss-1-A_eKY1YSy6uwyPYtV4
Message-ID: <CAJ-Vmo=A2W7-V8LC3dhktArdShmr+GTkQYrz5KufsZkxagzh8w@mail.gmail.com>
Subject: Re: cpuid_t typedef? (was Re: Processor cores not properly
 detected/activated?)
From: Adrian Chadd <adrian@freebsd.org>
To: John Baldwin <jhb@freebsd.org>
Content-Type: text/plain; charset=UTF-8
Cc: Attilio Rao <attilio@freebsd.org>,
 freebsd-current <freebsd-current@freebsd.org>,
 Jia-Shiun Li <jiashiun@gmail.com>, Alan Somers <asomers@freebsd.org>,
 Tim Bishop <tim-lists@bishnet.net>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 30 May 2014 16:09:47 -0000

On 30 May 2014 07:57, John Baldwin <jhb@freebsd.org> wrote:

>> Ugh. Ok. I was too deep in the trenches of device drivers and other
>> ancillary things doing bad things to char/short with cpu ids when
>> walking things. I totally missed kinfo_proc.
>>
>> I'll go think about it a bit more.
>
> It shouldn't be too hard to to handle kinfo_proc.  pf is another case.  It
> might be nice to have a way to auto-compute the right number of bits to
> reserve based on MAXCPU.

*nod*

ok. Let me go and start sprinkling things around.



-a