Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp672635ybl; Wed, 4 Dec 2019 09:03:10 -0800 (PST) X-Google-Smtp-Source: APXvYqxhjjzFnRwdeLgt9J8hR1iSVkCt3tQ66/UZAhdvAlhOk5YCAfkXbmn7hJkV++nu7SyDW6eq X-Received: by 2002:aca:4712:: with SMTP id u18mr1106197oia.93.1575478990641; Wed, 04 Dec 2019 09:03:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575478990; cv=none; d=google.com; s=arc-20160816; b=TKiynI5A4Jqkx4pYeLwsJJqQZ1iLM3Psch/BCOdNn2nB26RsGTTsPYNOhUFv21jWCl drkK/KpTve21uwiLE+OL8ka6UVO+22j9m7MMlRhf66Hebms0cQEGbXcd2pS4nUF/jkH/ t3g0kRCgATbj2nLRyMflW/PjLR7Abo+UutdxyNOj9wwbpsVJyTQNFsADmwoMUQmSjmOb 2qeA+RpuTRI0W+x8OhN/0Ff8q1vFmH5bmBm7tnHh7K0dMPmZP0NDAmAxAZ6h3+zCOiMI S7dZ4FzLWPDYqGg63sJGeW7OcjuOiGIebehQs+U93+lyU4UGgTB2jXlulgHbm/s9YFop 0lFw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :content-language:accept-language:message-id:date:thread-index :thread-topic:subject:to:from; bh=uz9dSQJ0iVMBY2g4MaqrHnEkmIEeNi3mw3FqyseEeno=; b=hs9K7DYBUke/PDsLk1IfzOlXnVW3HjvQsrEFQwrIN9lb0nIVw0mJsbHZN7JyyevHBi 0jzSLL9BvMpVIbeeAajZCp4SGHMDLDg02rnHm4S4olXtIr/S1wTQr3N491axklkD6RTB nTEW5tvpGjSjBnXDvaF0WgNji9XqwGgjUAlZ4ObWPOozuhaeIwRsatxCyNtTSXC5v6Xq VRnQzddQ3+n8Uco6nwAqltxu5BRLNMlSG0kAz4nFw2KyulF/YtgxmCBnzeDT0NFF/2w5 EbQE7LLlHvBM2KzIIavIYnDx5GwADK1kyq+MD9M+pCm2IGF3wBrzp2CjErplAli95yDO C2IA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w16si3564332oih.154.2019.12.04.09.02.45; Wed, 04 Dec 2019 09:03:10 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729000AbfLDRBf convert rfc822-to-8bit (ORCPT + 99 others); Wed, 4 Dec 2019 12:01:35 -0500 Received: from eu-smtp-delivery-151.mimecast.com ([146.101.78.151]:38428 "EHLO eu-smtp-delivery-151.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726934AbfLDRBf (ORCPT ); Wed, 4 Dec 2019 12:01:35 -0500 Received: from AcuMS.aculab.com (156.67.243.126 [156.67.243.126]) (Using TLS) by relay.mimecast.com with ESMTP id uk-mta-99-sjLWNHPnP_GIhzqPZuPVuA-1; Wed, 04 Dec 2019 17:01:32 +0000 Received: from AcuMS.Aculab.com (fd9f:af1c:a25b:0:43c:695e:880f:8750) by AcuMS.aculab.com (fd9f:af1c:a25b:0:43c:695e:880f:8750) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 4 Dec 2019 17:01:32 +0000 Received: from AcuMS.Aculab.com ([fe80::43c:695e:880f:8750]) by AcuMS.aculab.com ([fe80::43c:695e:880f:8750%12]) with mapi id 15.00.1347.000; Wed, 4 Dec 2019 17:01:32 +0000 From: David Laight To: "x86@kernel.org" , "linux-kernel@vger.kernel.org" Subject: Running an Ivy Bridge cpu at fixed frequency Thread-Topic: Running an Ivy Bridge cpu at fixed frequency Thread-Index: AdWqwtS5CEX1+9oiRRqqz+2UyKDrUw== Date: Wed, 4 Dec 2019 17:01:32 +0000 Message-ID: <8eeee0695c664305ba6a56bce42a995f@AcuMS.aculab.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.202.205.107] MIME-Version: 1.0 X-MC-Unique: sjLWNHPnP_GIhzqPZuPVuA-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Is there any way to persuade the intel_pstate driver to make an Ivy bridge (i7-3770) cpu run at a fixed frequency? It is really difficult to compare code execution times when the cpu clock speed keeps changing. I thought I'd managed by setting the 'scaling_max_freq' to 1.7GHz, but even that doesn't seem to be working now. It would also be nice to run a little faster than that - but without it 'randomly' going to 'turbo' frequencies (which it is doing even after I've set no_turbo to 1). An alternative would be a variable frequency TSC - might give more consistent values. David - Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)