Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp5283374rwl; Tue, 21 Mar 2023 16:40:09 -0700 (PDT) X-Google-Smtp-Source: AK7set+DmjoiLvDMVmaOoDppwHIKIwaZ9rrXaHUHfBfXVj3ilUZ6zABF2xpjBq8wKhmK1v0hoBlE X-Received: by 2002:a05:6a20:7da6:b0:db:4a66:88b7 with SMTP id v38-20020a056a207da600b000db4a6688b7mr394746pzj.4.1679442008882; Tue, 21 Mar 2023 16:40:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1679442008; cv=none; d=google.com; s=arc-20160816; b=HephextSmQZg8/7ijtNyR4yHQpAQ586c33p5CpTqUkgcudgnfLlFTA1CK8xFLiicTM B7ohE/VsotgT65K2qqDu6+b45ERz/G1c0EX4Gef/lMTZ5dtYSnW093gTdQ4K1EB97MxY 1gcyErbRpMaSCCSMWL+jl1rafDp0G9DDwCpio7SiHj69iC2J/ApxKsDryWCv8CUWvmaK VEVCkXnbZA5dcP6ffXbLA+ChRKGf4ddFP6sVLwqGszIss6hdM7plhywkzqoZvzsS8A0S U+JR2zDGmu5UpL+5XRuHkjSLqVeR5ASBuX1tDo9oknjG9xb2gkQX/Tk7RRRXBD6Dz47t oktw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-disposition:mime-version:reply-to :message-id:subject:cc:to:from:date:dkim-signature; bh=ogmGBIt+TB3L0RMjj+GgwDzfTgog/JkBseFOrD7boqE=; b=fRS1QmPjvPju6YqtwFJgBE2NOFREnVIgd1EP2cgYqV+WNvGqK3EFjMhHioZBp1nlXA WAghQ0/7CpWnnMPaGMWx+SRaBWiwXQobQfh5G68leaIDweVGsmsuP+h9+iYB8oJoTnaI J+9xFmn1o4z1v6DC6zTfo7BaKkbY++A7B+YbngOJZEQjJ7u/++aiuwSO+ET12XvSqMib zRuz2rvNJpItf87GT7av+a27QYdRcJLGGuWT3l8hS/VStnASrbrEpD5gqOr+TYNSGsve ZwtuvUGZudCGtqENC66MWKAi3FutPzHIAVgu0x5GWbrM5o7dIdC8XgvN+GPoUylXb/Eb hjdA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=sT91Amak; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s13-20020a63924d000000b0050973dc9f3asi14017520pgn.850.2023.03.21.16.39.57; Tue, 21 Mar 2023 16:40:08 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=sT91Amak; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229666AbjCUXXd (ORCPT + 99 others); Tue, 21 Mar 2023 19:23:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37002 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229511AbjCUXXc (ORCPT ); Tue, 21 Mar 2023 19:23:32 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8DB44574ED for ; Tue, 21 Mar 2023 16:23:31 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 24693B81907 for ; Tue, 21 Mar 2023 23:23:30 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D1C43C433EF; Tue, 21 Mar 2023 23:23:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1679441008; bh=ea87VpNLJUaOmFKXtk3vlpERWguAOEohFqyBipOJXA0=; h=Date:From:To:Cc:Subject:Reply-To:From; b=sT91AmakvkXJe17vPqbF0yzi89Cnnz8KII14Xw132PeiFNV36TmsGUw6o4w5aclLH kD+fdAz3joy+dQw4RqUuLuR1+QN6xOolCDEdmV3iQPGc+vlPpvC3QxPHQmH4zLOp+O LivwJfRfcCt9oRyEweIX7oVZscuYygU/bz0K/rUgWL+7/dRa4Abz/WBA3QsB7IGuyc 50MEEFiSnxK/dtIPJ4IIAlBlWewBzbvotO8XNMcVvFLrHo4Ll4WqZH4V7xT/EiDT8W lO66e75li1ooJ7Irw691Hyqp5OBwwCPTiMKxbsRXlbFRGkyv777s9/cfw+X51Hz8hp BjYk3WCRjq7pA== Received: by paulmck-ThinkPad-P72.home (Postfix, from userid 1000) id 6429B154033A; Tue, 21 Mar 2023 16:23:28 -0700 (PDT) Date: Tue, 21 Mar 2023 16:23:28 -0700 From: "Paul E. McKenney" To: feng.tang@intel.com Cc: linux-kernel@vger.kernel.org Subject: A couple of TSC questions Message-ID: Reply-To: paulmck@kernel.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-2.5 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, Feng! I hope that things are going well for you and yours! First, given that the kernel can now kick out HPET instea of TSC in response to clock skew, does it make sense to permit recalibration of the still used TSC against the marked-unstable HPET? Second, we are very occasionally running into console messages like this: Measured 2 cycles TSC warp between CPUs, turning off TSC clock. This comes from check_tsc_sync_source() and indicates that one CPU's TSC read produced a later time than a later read from some other CPU. I am beginning to suspect that these can be caused by unscheduled delays in the TSC synchronization code, but figured I should ask you if you have ever seen these. And of course, if so, what the usual causes might be. Thoughts? Thanx, Paul