Received: by 2002:a05:6a10:87d6:0:0:0:0 with SMTP id g22csp850372pxr; Mon, 11 Apr 2022 08:42:21 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxADcByvRnAXYxB5P4LEF33Em50Qf20vWxF3lBj8TeZsGk0tllZidayGwBmN/LUTD0EGO6l X-Received: by 2002:a17:90a:f3d6:b0:1cb:a0aa:5e60 with SMTP id ha22-20020a17090af3d600b001cba0aa5e60mr5885318pjb.161.1649691741815; Mon, 11 Apr 2022 08:42:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649691741; cv=none; d=google.com; s=arc-20160816; b=Rq0Ag5kjKm1rwrrJSc5RR1bi4fxOqT5QBTzCkhfs9hBc5aaap7sP1KRE3u+O+IBw+s prSIExA8NPvVS525ML+TKI34wyu47AIpZxCJAeuM9X7u/vj7q+cehCHqj/V7nfN2It3Y g3fSFtLL2WOqz1ksn0mqlg6Ax9Z+oSwHeK7AZS4SmjJ8A+621ta8nauVT4T46sSWDNZL I2XJ8i/sy9I6Lc4iGGib+V5udwdwgSWJnADbWz/5cZD+GguQWTp7ZQN7VJ4FWnZ1TJyk eiDUeKNs3gRrO7/b8PwafTIH6twLplGefKbCT7QzK1ZRiD0cLSwQ2EHhtJ7Y4tVf9Q4c sIkA== 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=oM+FoGv/BkTkG2TdHv8UkTd+jiQ2ziLqcW0PI5BxId8=; b=aiW0bvfWs1n9gOKaFbb2oXQt0cSkOIQH2vA1HTpMFn/Sakvb7ASVpS+RbmsIjUmfGI KfMpbb5jed/IMmNbPg+w2n7Ymaabxc0QUiMZXQsrYohUBwA7B1JjJS1HOL1l/xGRHksL anekGc0N1W0w5ikFmnj7WUgTdsUKGMxGIgWPOqja0oA7JHuEONn0T8eUPRf7g/sOF070 HNeDFA6Pa1qGp5u01VpgRbq7AyCgkgN0icpBIMY3BqOa2w6exHGmN84pONleIQ69szD5 esGkB6lkshZ3N281+WVjouHi48XVOyry4DlQrodrQ/4pHY5sSGujXX+kcCTJVfr7/dWz 31Cg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=RJ3g47WF; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e header.b=v+XCuAeD; 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 h62-20020a638341000000b003816043f008si105299pge.509.2022.04.11.08.42.06; Mon, 11 Apr 2022 08:42:21 -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=RJ3g47WF; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e header.b=v+XCuAeD; 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 S240868AbiDIIPo (ORCPT + 99 others); Sat, 9 Apr 2022 04:15:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38618 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230343AbiDIIP0 (ORCPT ); Sat, 9 Apr 2022 04:15:26 -0400 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C387A674F0; Sat, 9 Apr 2022 01:13:20 -0700 (PDT) From: Kurt Kanzenbach DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1649491999; 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=oM+FoGv/BkTkG2TdHv8UkTd+jiQ2ziLqcW0PI5BxId8=; b=RJ3g47WFm501Wsc7a9Pc5BI3r/v+TZVkRFbVskQ9OA/vtf7diHW8GOxpwN0OjYnOl3cWvH V8zwNI+H645fJ8qK38iBrXLvxzt/M4zGpCRHCMGdjv/6JIKldxAXKb0+5488FVLRrAqTu4 FdhMYkIzer+9Pn+WIS6WVdjTYkLAkgAIOgo/1n46l68lbS2PXCEtZTBvBeQVd/OoYDHPLe rkZyayYQSeZ78dLxC5efEwKBYKSrL+T/wQKC02xj/R7xBxoGzfKQ8FAUAKWUQ3VRvlk2IM 8DfNxUS2JgJYxzfE471Rw3frvW/vj3QLmWQXNbbrU6LCQPCWhDE9dxRiRLhMzg== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1649491999; 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=oM+FoGv/BkTkG2TdHv8UkTd+jiQ2ziLqcW0PI5BxId8=; b=v+XCuAeDY6E9LehoYbDZmkqdjG0BKLsseED+lKx6+nUBcdJnfzPjov3fYy203ZyXQFwslg n/BsRLw11Sgpx6Bw== 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 3/3] tracing: Add documentation for trace clock tai Date: Sat, 9 Apr 2022 10:13:00 +0200 Message-Id: <20220409081300.4762-4-kurt@linutronix.de> In-Reply-To: <20220409081300.4762-1-kurt@linutronix.de> References: <20220409081300.4762-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 new 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