From owner-freebsd-arch@FreeBSD.ORG Tue Jul 29 17:52:02 2014 Return-Path: Delivered-To: freebsd-arch@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 5C4AF819; Tue, 29 Jul 2014 17:52:02 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 33A222F0B; Tue, 29 Jul 2014 17:52:02 +0000 (UTC) Received: from [192.168.1.75] (75-48-77-17.lightspeed.cncrca.sbcglobal.net [75.48.77.17]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 8A5B9B91C; Tue, 29 Jul 2014 13:51:59 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [rfc] where to put cpuid_t ? From: John Baldwin In-Reply-To: Date: Tue, 29 Jul 2014 10:51:57 -0700 Content-Transfer-Encoding: 7bit Message-Id: <41D207A0-D82F-456E-B0A4-9CA9520D4F77@FreeBSD.org> References: To: Adrian Chadd X-Mailer: Apple Mail (2.1878.6) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 29 Jul 2014 13:52:00 -0400 (EDT) Cc: "freebsd-arch@freebsd.org" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jul 2014 17:52:02 -0000 On Jul 24, 2014, at 12:03 AM, Adrian Chadd wrote: > Hi! > > I've been chipping away at a cpuid_t in a local branch for a while and > I think I have the very basics working well enough. > > However, the most annoying thing that's crept up is the most bikeshed > topic of them all - where should it live. > > I'd like to avoid having to include sys/pcpu.h or sys/_cpuset.h just > for the id type - it seems a bit overkill. > > So - suggestions? Otherwise I'm going to leave it in sys/pcpu.h and > just polluate appropriately. > > I'd like to try and get cpuid_t and a handful of KBI-changing things > into -HEAD before 11 is branched so we at least have a hope of trying > to support > 128 CPUs out of the box in the immediate future and > 253 > CPUs in the later future. __cpuid_t should be in and cpuid_t should be in . This is how the old cpumask_t worked (though it allowed __cpumask_t to be MD whereas I think you can probably make __cpuid_t MI). -- John Baldwin