From owner-freebsd-arch@FreeBSD.ORG Sat Mar 7 09:43:40 2015 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8290A8E3 for ; Sat, 7 Mar 2015 09:43:40 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 531CF773 for ; Sat, 7 Mar 2015 09:43:40 +0000 (UTC) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.14.9/8.14.9) with ESMTP id t279hWwo031271 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sat, 7 Mar 2015 01:43:33 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <54FAC83F.7020008@freebsd.org> Date: Sat, 07 Mar 2015 01:43:27 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-arch@freebsd.org Subject: Re: RFC: Simplfying hyperthreading distinctions References: <1640664.8z9mx3EOQs@ralph.baldwin.cx> <2092193.qt8NhEKglv@ralph.baldwin.cx> In-Reply-To: <2092193.qt8NhEKglv@ralph.baldwin.cx> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Mar 2015 09:43:40 -0000 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.