From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 10 15:56:22 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ADC4CD2A for ; Tue, 10 Mar 2015 15:56:22 +0000 (UTC) Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0081.outbound.protection.outlook.com [207.46.100.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6B22D227 for ; Tue, 10 Mar 2015 15:56:21 +0000 (UTC) Received: from DM2PR0801MB0944.namprd08.prod.outlook.com (25.160.131.27) by DM2PR0801MB0943.namprd08.prod.outlook.com (25.160.131.26) with Microsoft SMTP Server (TLS) id 15.1.106.15; Tue, 10 Mar 2015 15:56:13 +0000 Received: from DM2PR0801MB0944.namprd08.prod.outlook.com ([25.160.131.27]) by DM2PR0801MB0944.namprd08.prod.outlook.com ([25.160.131.27]) with mapi id 15.01.0106.007; Tue, 10 Mar 2015 15:56:13 +0000 From: "Pokala, Ravi" To: "lokadamus@gmx.de" , Rui Paulo Subject: Re: detecting hyperthreading Thread-Topic: detecting hyperthreading Thread-Index: AQHQWqyImRFHWPGSCkqtx00nVjUfFZ0U6yCA//+MIICAAWfagP//i6mA Date: Tue, 10 Mar 2015 15:56:12 +0000 Message-ID: References: <9F2E1411-B517-4BC8-AF61-BB15EE35083C@me.com> <54FF1343.1020705@gmx.de> In-Reply-To: <54FF1343.1020705@gmx.de> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.8.150116 x-originating-ip: [24.6.178.251] authentication-results: gmx.de; dkim=none (message not signed) header.d=none; x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0801MB0943; x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10009020)(6009001)(377424004)(51704005)(164054003)(13464003)(40100003)(19580405001)(19580395003)(2950100001)(92566002)(76176999)(46102003)(50986999)(99286002)(54356999)(83506001)(122556002)(102836002)(36756003)(62966003)(221733001)(77156002)(2501003)(2656002)(93886004)(87936001)(86362001)(2900100001)(106116001)(66066001)(7059030); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR0801MB0943; H:DM2PR0801MB0944.namprd08.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002009)(5005006); SRVR:DM2PR0801MB0943; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0801MB0943; x-forefront-prvs: 051158ECBB Content-Type: text/plain; charset="us-ascii" Content-ID: <5156B82CBDF092489A8C7E5B4996D663@namprd08.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: panasas.com X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Mar 2015 15:56:12.5101 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: acf01c9d-c699-42af-bdbb-44bf582e60b0 X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0801MB0943 Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2015 15:56:22 -0000 -----Original Message----- From: "lokadamus@gmx.de" Date: 2015-03-10, Tuesday at 08:52 To: Ravi Pokala , Rui Paulo Cc: "freebsd-hackers@freebsd.org" Subject: Re: detecting hyperthreading >Have you look at dmesg? >My system is a P4 with HTT. >dmesg |more [...] >CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3000.00-MHz 686-class CPU) > Origin =3D "GenuineIntel" Id =3D 0xf29 Family =3D 0xf Model =3D 0x2 >Stepping =3D 9 > >Features=3D0xbfebfbffCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Features2=3D0x4400 Of course. :-) But there are two problems: (1) That just tells me HTT is supported by the CPU, not that if kernel is using it. (2) It's difficult to parse. Of the two, (1) is the bigger concern for my use-case. Thanks, Ravi