From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 19:23:14 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9889816A47D for ; Mon, 25 Jun 2007 19:23:14 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (vlk.vlakno.cz [62.168.28.247]) by mx1.freebsd.org (Postfix) with ESMTP id 4D66813C448 for ; Mon, 25 Jun 2007 19:23:13 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 567CA8BE983; Mon, 25 Jun 2007 21:23:10 +0200 (CEST) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (vlk.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0f6WFqVDzHeF; Mon, 25 Jun 2007 21:23:09 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 3862D8BE922; Mon, 25 Jun 2007 21:23:09 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.13.8/8.13.8/Submit) id l5PJN8ZK014597; Mon, 25 Jun 2007 21:23:08 +0200 (CEST) (envelope-from rdivacky) Date: Mon, 25 Jun 2007 21:23:08 +0200 From: Roman Divacky To: Stephen Montgomery-Smith Message-ID: <20070625192308.GA14544@freebsd.org> References: <467EF0C1.1010609@optiksecurite.com> <467FFF41.10204@math.missouri.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <467FFF41.10204@math.missouri.edu> User-Agent: Mutt/1.4.2.3i Cc: freebsd-hackers@freebsd.org Subject: Re: CPUTYPE in general - was Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 19:23:14 -0000 > In general, how does one decide which CPUTYPE to use? The connection > between the options for CPUTYPE and the output of dmesg is not so > obvious to me. I looked at the features advertised by dmesg (which in > my case included SSE3) and then reverse engineered bsd.cpu.mk to figure > out I should be using "prescott," but I am hoping I figured it out the I would not judge only by instructions like SSE etc. ins scheduling etc. plays key role as well. you should know what cpu you bought, or just use cpuid (found in ports) and determine what cpu you have. on -current you can set _native_ or native (dont remember) and gcc will choose itself... ;) roman