Received: by 10.223.164.202 with SMTP id h10csp431479wrb; Wed, 15 Nov 2017 02:06:38 -0800 (PST) X-Google-Smtp-Source: AGs4zMabsnSegJus05Qpvn8vEQBszWiPCPmVWKHVWa/ViapappYQ/W/pWNstcTaMnYvU3jdah9WD X-Received: by 10.98.57.131 with SMTP id u3mr16870666pfj.7.1510740398539; Wed, 15 Nov 2017 02:06:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510740398; cv=none; d=google.com; s=arc-20160816; b=07Cv9mDyDYmj2zBvaEeRkO3ZBRsCi0cFEd3toMXjJ6rWHXRoYocySBx572QMUVfPsi hQXz1jLrUaS6Db8+gkhHcPTtkHRZubSyiI/xbbUzbvkxEPmDcO2S2rXzaIqxP4O+uX1U DIH3qeRsL6Pf6Xm9E5iF8nXMsYBDbwDhqhTNLqzD4lpzou3A4bSsVngKKKALpQmI3O27 iLyh+wnblT4gXL/+RSSspCkvn4S064bMlPRwTjL6nGdkpW1wTnzWKYyqMMeuYtVtMae5 pceH8e3u53l3nctLB/iiC0IAaErAfq+Dh5sHwo3VlwGQEHHewztKlYKS5MZPpKlQsazA tF7A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=IPcyjFmopBcAg1WFZUvYjb1dJUI4B0i8gYy0EZMKKRg=; b=Gj/6RCV5iwVKD+LQLzChuDrEp7gd/4jgFt1OYadLnN8djYJuaDw0obHCYx93fgpEQ5 i61hlPZ44bUukAwspqZ4Uj7T1HIdKcYkPyoHvIJH2Ca7fG871Tvq0aF7fjax2YMcjzxE yx8i38HXyPRe+N+BN0eLXWH/EUfxP7tDQ7554a2zSQlOKBDHceuga2ZEDyBh0GW8jc+i IxoSiQMpLaBu0Tdnk1gkwCK4wU49CG3GENUm6/dE129KX41yxFgKQYtft2BZtpT0Gv9k jeY7Nt1FDR1gSBbNvHGwDVE1geV1PfH59a0+kSQ97O3Gn8mTHa3NHnCUBeND7YkKdJ6v 05gg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=a9n9RKWp; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q186si13254914pga.657.2017.11.15.02.06.26; Wed, 15 Nov 2017 02:06:38 -0800 (PST) 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; dkim=pass header.i=@linaro.org header.s=google header.b=a9n9RKWp; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757335AbdKOKFd (ORCPT + 88 others); Wed, 15 Nov 2017 05:05:33 -0500 Received: from mail-ot0-f179.google.com ([74.125.82.179]:51446 "EHLO mail-ot0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755502AbdKOKFV (ORCPT ); Wed, 15 Nov 2017 05:05:21 -0500 Received: by mail-ot0-f179.google.com with SMTP id b54so7038295otd.8 for ; Wed, 15 Nov 2017 02:05:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IPcyjFmopBcAg1WFZUvYjb1dJUI4B0i8gYy0EZMKKRg=; b=a9n9RKWpj/dA366LD6vIuhyOnsmqNu8c9S5lvUjwpN3SDmwDRaFHmYiufm40nMDqd3 YWCeIzuV64IMcCPD7KilX4c8hub2645sAWpP95NM4geFhqVB/Qc9Rf37QNqO8GQpfYZo ivu3NBcwD/xM4q6Q5tFqBoSGv8bBl2jMjwhDg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IPcyjFmopBcAg1WFZUvYjb1dJUI4B0i8gYy0EZMKKRg=; b=YUPpbG7Oru3jxadbHAKKgRj6WR2/yw3kpBNL4ePyohbaJikCkMHzcZph7xMiFn7bmn hx8dG5kxSxwv6be52tD4UCNefN2yP2RChnVkebMtMkSr4PiivHVm50lj4IKJlTGvlxJK U/HqkVDIT2b4qBT1ONgZyYRRxYK2xeXyeJWoEC9pfLYGF6ziLuapNzhjWkEjhSiEOIw0 4pcl94+cIlou93+zC2N6E0y4ebtuSVYFkLCPKisr7IJdzO4QTyainBHxp4cDYhCTYrwz D2vMAwdWM+QUd8ZeXvbDFf+EcQVOUKHauTSlxr1leJZbj+CJ54VvLIWbQ8kUKvhv7Pmb Xw9w== X-Gm-Message-State: AJaThX6SaA0Zg9id/YwjvglZfw1rrV/7sn/aaHuLYwrfFZkqLhsdIPlb JGB362WAzLHwtamK0e5BP1ZFS0s9Lv72EGFljlqprA== X-Received: by 10.157.67.131 with SMTP id t3mr7443916ote.87.1510740320964; Wed, 15 Nov 2017 02:05:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.7.132 with HTTP; Wed, 15 Nov 2017 02:05:20 -0800 (PST) In-Reply-To: <20171115092539.xrenngsxvsxzizs3@piout.net> References: <354301cc7c61ba39021bb56e7ede5ba959e9dbb2.1510730564.git.baolin.wang@linaro.org> <20171115092539.xrenngsxvsxzizs3@piout.net> From: Baolin Wang Date: Wed, 15 Nov 2017 18:05:20 +0800 Message-ID: Subject: Re: [PATCH] rtc: Add tracepoints for RTC system To: Alexandre Belloni Cc: Alessandro Zummo , Steven Rostedt , Ingo Molnar , linux-rtc@vger.kernel.org, LKML , Arnd Bergmann , Mark Brown Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Alexandre, On 15 November 2017 at 17:25, Alexandre Belloni wrote: > Hi, > > On 15/11/2017 at 15:30:21 +0800, Baolin Wang wrote: >> It will be more helpful to add some tracepoints to track RTC actions when >> debugging RTC driver. Below sample is that we set/read the RTC time, then >> set 2 alarms, so we can see the trace logs: > > I'm not sure it is actually useful when debugging an RTC driver because > you will be interested in the real values that are written to or read > from the RTC, not what is returned by the driver to the RTC core as this > information is already readily available to userspace. > > Is this really worth the added overhead? > > Maybe you have another use case? Suppose one case like one thread set one alarm into RTC unexpectedly, which maybe affect the system suspend. So we can catch out which thread set the RTC alarm by trace logs. From trace log, I also can know who set the RTC time, when and who disable the alarm irq to debug some cases like the alarm event was not fired. In some respects I think it will be helpful, maybe I need delete some unuseful trace events? Thanks. -- Baolin.wang Best Regards From 1584125622100654916@xxx Wed Nov 15 09:58:39 +0000 2017 X-GM-THRID: 1584116430602610856 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread