Date: Sat, 07 Mar 2015 01:43:27 -0800 From: Julian Elischer <julian@freebsd.org> To: freebsd-arch@freebsd.org Subject: Re: RFC: Simplfying hyperthreading distinctions Message-ID: <54FAC83F.7020008@freebsd.org> In-Reply-To: <2092193.qt8NhEKglv@ralph.baldwin.cx> References: <1640664.8z9mx3EOQs@ralph.baldwin.cx> <CAJ-VmoknoYw-jkihmutN6qB=Piy4O73bzV50ijDaEaNvEncGpA@mail.gmail.com> <2092193.qt8NhEKglv@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/6/15 3:41 PM, John Baldwin wrote: > We are now in the odd situation where we refer to a small (and > shrinking) set of CPUs that support HTT as HTT and we refer to a > much larger (and growing) set of CPUs that support HTT as something > else. This means that if a random user wants to see if FreeBSD > supports HTT they won't see that in dmesg on a modern CPU without > having some sort of magic decoder ring. I like the HTT (SMT variant) idea. More information is better.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54FAC83F.7020008>