Received: by 10.213.65.68 with SMTP id h4csp1165840imn; Wed, 4 Apr 2018 13:52:41 -0700 (PDT) X-Google-Smtp-Source: AIpwx48NLEZGT8rmWWfMfzI72Y+9mlYkaznFGv0U8yEhS0JRlSiAoAfD2Z7yx6xA4VirvcDBgG1Y X-Received: by 10.98.60.4 with SMTP id j4mr14914387pfa.229.1522875161355; Wed, 04 Apr 2018 13:52:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522875161; cv=none; d=google.com; s=arc-20160816; b=yw77ozVtbjv8kYQBdPlnWkVHZFYuiLqO09RxAz0lXBE/lPL6SzELhTK0OG9/7sRVNP 8ihCiynBgaWt8OGylePfM+j9911kDQtQgAkq8nPAHHL6xq30GT+NQi9iPqePanPDOqdj RHmr6Y2YtK9ZkrDHrswEPkMh6F/t4NbPCS4pmhC0NOV0C7KnroY6KA0ex7KAtLeuFUgk dDgWnRBw0U3TT+LnyuNICTjJsWNt9knXBKDw+0jY69pmefpt4qru/GzUKEyur1XkutiK FasiRvGhgF6+8M/G+BJ7uJuVFWy+bYzfF/3M6dvj80V/JZeqBSXv3vG8IHhQB23dgrw2 wBHw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:arc-authentication-results; bh=ipgKs17uuvFta4taDCRMvsoGJvJ3fOOiLaiDX+R89JY=; b=aoAABATahlhbdkxSaVnbZL2hoN+KqTyvEmiylR/pkdRvvaBhjNHkvbblYYXR9bY1En ED8bKjMUE1jXV1SSIzJ0zQvx8jRas/fAkUaOb6lYVtiY6a5cxp5ePOIJ9pRt12GxefO9 lLHyksMs7yq4pYQ6zru2SP8qwHNY22yi9RHjCm6uUkWv/beQRCjRX3plKPgHiPfhHYd/ YYEaxrXryVMmXrALAIjHgHYR9q9+cMEEYO4oL9dPegHZ8VQwevhWOFAzTkUACEoWPhCm klJhVFpUh92M/VBWBkGGAikDRNpfN2+tLbFbccuL4iukoL9cTF0kHlOV9+oSQPyR3EPI BLCA== 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 m12si4304867pgs.18.2018.04.04.13.52.26; Wed, 04 Apr 2018 13:52:41 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752198AbeDDUvS (ORCPT + 99 others); Wed, 4 Apr 2018 16:51:18 -0400 Received: from mail.fireflyinternet.com ([109.228.58.192]:51934 "EHLO fireflyinternet.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751849AbeDDUvR (ORCPT ); Wed, 4 Apr 2018 16:51:17 -0400 X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=78.156.65.138; Received: from haswell.alporthouse.com (unverified [78.156.65.138]) by fireflyinternet.com (Firefly Internet (M1)) with ESMTP id 11263448-1500050 for multiple; Wed, 04 Apr 2018 21:51:03 +0100 Received: by haswell.alporthouse.com (sSMTP sendmail emulation); Wed, 04 Apr 2018 21:51:03 +0100 From: Chris Wilson To: linux-kernel@vger.kernel.org Cc: intel-gfx@lists.freedesktop.org, Chris Wilson , Steven Rostedt Subject: [PATCH v3] trace: Default to using trace_global_clock if sched_clock is unstable Date: Wed, 4 Apr 2018 21:51:02 +0100 Message-Id: <20180404205102.20816-1-chris@chris-wilson.co.uk> X-Mailer: git-send-email 2.16.3 In-Reply-To: <20180330150132.16903-1-chris@chris-wilson.co.uk> References: <20180330150132.16903-1-chris@chris-wilson.co.uk> X-Originating-IP: 78.156.65.138 X-Country: code=GB country="United Kingdom" ip=78.156.65.138 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Across suspend, we may see a very large drift in timestamps if the sched clock is unstable, prompting the global trace's ringbuffer code to warn and suggest switching to the global clock. Preempt this request by detecting when the sched clock is unstable (determined during late_initcall) and automatically switching the default clock over to trace_global_clock. This should prevent requiring user interaction to resolve warnings such as: Delta way too big! 18446743856563626466 ts=18446744054496180323 write stamp = 197932553857 If you just came from a suspend/resume, please switch to the trace global clock: echo global > /sys/kernel/debug/tracing/trace_clock Signed-off-by: Chris Wilson Cc: Steven Rostedt (VMware) --- v2: Tell the user what's happening and what they can do to correct it. v3: Restore the correct logic to switch only if the default trace clock (no override) is found to be *not* stable. --- kernel/trace/trace.c | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c index 13baf85b27d8..a1810b053f65 100644 --- a/kernel/trace/trace.c +++ b/kernel/trace/trace.c @@ -41,6 +41,7 @@ #include #include #include +#include #include #include "trace.h" @@ -8505,3 +8506,21 @@ __init static int clear_boot_tracer(void) fs_initcall(tracer_init_tracefs); late_initcall_sync(clear_boot_tracer); + +#ifdef CONFIG_HAVE_UNSTABLE_SCHED_CLOCK +__init static int tracing_set_default_clock(void) +{ + /* sched_clock_stable() is determined in late_initcall */ + if (!trace_boot_clock && !sched_clock_stable()) { + printk(KERN_WARNING + "Unstable clock detected, switching default tracing clock to \"global\"\n" + "If you want to keep using the local clock, then add:\n" + " \"trace_clock=local\"\n" + "on the kernel command line\n"); + tracing_set_clock(&global_trace, "global"); + } + + return 0; +} +late_initcall_sync(tracing_set_default_clock); +#endif -- 2.16.3