Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1162438imm; Fri, 13 Jul 2018 12:41:35 -0700 (PDT) X-Google-Smtp-Source: AAOMgpdxKGJTeYPMOpRXS+l5iVvePhpK9CgJ5rnIoRe7kw8zKAXmKaccCj8b2jV/og3wVcMG1rc3 X-Received: by 2002:a62:700a:: with SMTP id l10-v6mr8325052pfc.71.1531510894981; Fri, 13 Jul 2018 12:41:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531510894; cv=none; d=google.com; s=arc-20160816; b=NgX91mxmmrdpBQW6ADaA2Cl+Sf92qs43eFfueZ8yh6DKxRzTQI4cLUFb0YZua6J7/O zkhlZAYxdHKQ0GQcCXbzgfFktl16mi7RjF/4ROG44mTvoI3r4IBVMxMZi3LqxeLIeHFb FSF84kekof+tCSubnYdbvnCs3PmCNYO0t75AXrxzyHAgTUIE8vED8FnLwCxo2hEeVpcE 8nYWRM+WaMLGIZJGT0DbvqHsXmy8SadU6NiiwEg13B2JJjrArCXH8WXq0XyFoETqj3BL WQ1WVdTCL/x8Ml4Wt77hsAGyO7rOxv+fyRR3rI4J7DFuaQi+9LRaFS3RLcldm0qipU3L mxjg== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=j0bqbFpM+5BRbYISQvsR6CV3SSMVyHVpKVvhG62NTuI=; b=GKkoTJpDQqLPBUc/lnE0LdK4iMGbuzZWmzVK5aQ77il8whGWhLtKVKQAcmRur0Y9Y+ teVG5qc7kXCDKPvMhAjv+OPrf60rEzV2QuTsd5pbWTiY8la9EgPBC5504ts02NNPSTcl EIqXhcZfDXG5ouTT9QZHvsBMdoGOuhLSv0M1nDkjRbODIiX2JZ9dW2Ekvt/nSCih4Je6 q9Lx8NdcN0/n/kBTcwwcF1DiNkSAIpBbgh+BwlAFEj2/a80cmoC4XLLsS7jx8VaeiXOW h4Irt1x+QINkvEX/36mkmA9Y6MC66cKFjMsGZvRY4gog2/uyEj5MxylTH9YeGMdlqKfy OpPg== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z13-v6si26079518pfc.118.2018.07.13.12.41.20; Fri, 13 Jul 2018 12:41:34 -0700 (PDT) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731871AbeGMT4m (ORCPT + 99 others); Fri, 13 Jul 2018 15:56:42 -0400 Received: from mga06.intel.com ([134.134.136.31]:51452 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730149AbeGMT4m (ORCPT ); Fri, 13 Jul 2018 15:56:42 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Jul 2018 12:40:42 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.51,349,1526367600"; d="scan'208";a="57488756" Received: from avandeve-mobl.amr.corp.intel.com (HELO [10.24.10.60]) ([10.24.10.60]) by orsmga006.jf.intel.com with ESMTP; 13 Jul 2018 12:40:41 -0700 Subject: Re: [RFC] x86, tsc: Add kcmdline args for skipping tsc calibration sequences To: patrickg , len.brown@intel.com, linux-kernel@vger.kernel.org Cc: mingo@kernel.org, alek.du@intel.com, feng.tang@intel.com References: From: Arjan van de Ven Message-ID: <9cdcf3bb-4d01-19cc-536f-4745ecb058c6@linux.intel.com> Date: Fri, 13 Jul 2018 12:40:41 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7/13/2018 12:19 PM, patrickg wrote: > This RFC patch is intended to allow bypass CPUID, MSR and QuickPIT calibration methods should the user desire to. > > The current ordering in ML x86 tsc is to calibrate in the order listed above; returning whenever there's a successful calibration. However there are certain BIOS/HW Designs for overclocking that cause the TSC to change along with the max core clock; and simple 'trusting' calibration methodologies will lead to the TSC running 'faster' and eventually, TSC instability. > that would be a real violation of the contract between cpu and OS: tsc is not supposed to change for the duration of the boot > I only know that there's a use-case for me to want to be able to skip CPUID calibration, however I included args for skipping all the rest just so that all functionality is covered in the long run instead of just one use-case. wouldn't it be better to start the detailed calibration with the value from CPUID instead; that way we also properly calibrate spread spectrum etc... I thought we switched to that recently to be honest...