Date: Fri, 30 May 2014 09:09:45 -0700 From: Adrian Chadd <adrian@freebsd.org> To: John Baldwin <jhb@freebsd.org> 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> Subject: Re: cpuid_t typedef? (was Re: Processor cores not properly detected/activated?) Message-ID: <CAJ-Vmo=A2W7-V8LC3dhktArdShmr%2BGTkQYrz5KufsZkxagzh8w@mail.gmail.com> In-Reply-To: <201405301057.23736.jhb@freebsd.org> References: <CAJ-VmonhjQZGhxTjgJA5a3Cyu%2Bx7HCmuK1MDoLQtdpHJ4wR-FA@mail.gmail.com> <201405291729.33471.jhb@freebsd.org> <CAJ-Vmom5OBvj8b48SBgYpmK0u0E4%2Bs7ar4E_YmjVifnHAeBhEw@mail.gmail.com> <201405301057.23736.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=A2W7-V8LC3dhktArdShmr%2BGTkQYrz5KufsZkxagzh8w>