Received: by 2002:a05:6a10:6d10:0:0:0:0 with SMTP id gq16csp1795278pxb; Thu, 14 Apr 2022 14:22:09 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxIIHUPKto/z7SBg73uh9uAGAZ8f6gL9YY2g1hCFcTG1HdLSYjPl3zH3fM3eAxe0eVgJAPa X-Received: by 2002:a05:6402:681:b0:419:dbec:9909 with SMTP id f1-20020a056402068100b00419dbec9909mr5013587edy.310.1649971329049; Thu, 14 Apr 2022 14:22:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649971329; cv=none; d=google.com; s=arc-20160816; b=Sql3Vr2dbQbwmErc3qSlv8GZ/yZKrcHBaaW0w60saQd8hzyTBBzv97gbWv4RXBxUPK HWvnr3sMLB2v2ODp1DD9DfV1LQ+z3PsoXMcI4cVULYh97j0tQPGb4VkOJwS9/OmWSa3E mfmUeAFmgL85BlmzHey/whnfEG1IUGK475gMXMITw8CRGt/UiHStYzL2531gjBrk6vdV M1nUuTrBjUF8Dd4/9TWqnwP3WCpP+zjbadqOS72trq2OEpbb2IHe5LgumOqtN8kaBrO/ DqAmZfcqKtir5Lbv6aBZtmOCIvyBXC8P2TnEmm/+6W4aak992WxveJyxSkkhjuq7LNfh xBVw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:dkim-signature :dkim-signature:from; bh=iLmCDPlHlx+4vJ7+eT/pCoYu1/+sbjT/6wC8EGaZi10=; b=NioolvBfzqSIUY1+55D6UTIvc9QvYYTYqa3H70d54gN5AZg4x3ApmI3WUeVS2ho/vf FR2PAv5lwddW5HNPn5uto0xHqAIBMKIQFWA1sJJDSXedr1Vrfz1AQoKnlrABTBC5ojdH XSN+qOYpfQCPmHkyBr5jySFGiLTBCt1SBI4+U+5QuE4kDPO78J9VIGQXOTLSXrGNkMln FFusNDL7uQIpxGq0IM1HOlbrWZO3q/Rz0r7NkJl3/iqwoplRGFeYaESOmauBJAUIITQA 9yEAaapAHsSRtDh8hNxeA9Rk541E1XkMrZHRIaJ2g2sliZRrwZNatfIU+YFqDsjMrpu/ U3qQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=Ouz9SoFs; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e; 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=QUARANTINE dis=NONE) header.from=linutronix.de Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w13-20020a056402268d00b0041c7cde74fasi5049669edd.308.2022.04.14.14.21.43; Thu, 14 Apr 2022 14:22:09 -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=@linutronix.de header.s=2020 header.b=Ouz9SoFs; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e; 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=QUARANTINE dis=NONE) header.from=linutronix.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241299AbiDNJUx (ORCPT + 99 others); Thu, 14 Apr 2022 05:20:53 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40858 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241602AbiDNJUj (ORCPT ); Thu, 14 Apr 2022 05:20:39 -0400 Received: from galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 10E1251E4D; Thu, 14 Apr 2022 02:18:15 -0700 (PDT) From: Kurt Kanzenbach DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1649927893; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=iLmCDPlHlx+4vJ7+eT/pCoYu1/+sbjT/6wC8EGaZi10=; b=Ouz9SoFspDW418thOwaQ0Wmr2WP5cb7znTdJES07Jqk9ljP7qEuX4Ja0bp2p9Bx1rL46+0 KEM/ThW4kR7QqxstcwNG1UBJMbrSEcivkYgDo2AA3pJHs6Vv+FzGnev/fhr1PZlTqUDAWd 6f2Z2ddOjcAn5KCI+LKeV41G5Wyutpu08s+KxiTMHy/EPTRQLGrsB+Xt4YKuI6fXJkLvno 4K89hh3dbaTp+7PlMhnUVQK4fYa+WiGDSzXbiAzGiLOtHyRA3iNtaSgJD9QlQ+dOltQ2nK RblARhI6wi4jP2x1Os0ZUdTxZUAMvhPMUzyZMgTeX2JXgl3mXcUdKIDh8hJV+g== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1649927893; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=iLmCDPlHlx+4vJ7+eT/pCoYu1/+sbjT/6wC8EGaZi10=; b=Fup1SrnNBv5FuCo7x/lZ5UGJZXakS/VRTQw77bfksXFJPu8+Pso4qvtggfACDwPEjBiz36 3b1SHOh6BLCvwJAA== To: John Stultz , Thomas Gleixner , Stephen Boyd , Steven Rostedt , Ingo Molnar , Jonathan Corbet Cc: Richard Cochran , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Kurt Kanzenbach Subject: [PATCH v2 3/3] tracing: Add documentation for trace clock tai Date: Thu, 14 Apr 2022 11:18:05 +0200 Message-Id: <20220414091805.89667-4-kurt@linutronix.de> In-Reply-To: <20220414091805.89667-1-kurt@linutronix.de> References: <20220414091805.89667-1-kurt@linutronix.de> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham 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 Add documentation for newly introduced trace clock "tai". This clock corresponds to CLOCK_TAI. Signed-off-by: Kurt Kanzenbach --- Documentation/trace/ftrace.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/Documentation/trace/ftrace.rst b/Documentation/trace/ftrace.rst index 45b8c56af67a..b37dc19e4d40 100644 --- a/Documentation/trace/ftrace.rst +++ b/Documentation/trace/ftrace.rst @@ -517,6 +517,18 @@ of ftrace. Here is a list of some of the key files: processing should be able to handle them. See comments in the ktime_get_boot_fast_ns() function for more information. + tai: + This is the tai clock (CLOCK_TAI) and is derived from the wall- + clock time. However, this clock does not experience + discontinuities and backwards jumps caused by NTP inserting leap + seconds. Since the clock access is designed for use in tracing, + side effects are possible. The clock access may yield wrong + readouts in case the internal TAI offset is updated e.g., caused + by setting the system time or using adjtimex() with an offset. + These effects are rare and post processing should be able to + handle them. See comments in the ktime_get_tai_fast_ns() + function for more information. + To set a clock, simply echo the clock name into this file:: # echo global > trace_clock -- 2.30.2