From: John Stultz <john.stultz@linaro.org>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Mark Brown <broonie@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer
Date: Tue, 30 Aug 2016 11:58:46 -0700 [thread overview]
Message-ID: <CALAqxLXdeQ5snMbCxZRowu_BRDA+DXKLR3YE39tB7NDrAzmpig@mail.gmail.com> (raw)
In-Reply-To: <CAMz4kuLCU=vP7tuhh2a9XRk1KLKfkmJeW8YqXWDZVODtTrKqfA@mail.gmail.com>
On Tue, Aug 30, 2016 at 4:50 AM, Baolin Wang <baolin.wang@linaro.org> wrote:
> Hi,
>
> On 22 August 2016 at 12:23, Baolin Wang <baolin.wang@linaro.org> wrote:
>> For system debugging, we usually want to know who sets one alarm timer, the
>> time of the timer, when the timer started and fired and so on. Thus adding
>> tracepoints can help us trace the alarmtimer information.
>>
>> For example, when we debug the system supend/resume, if the system is always
>> resumed by RTC alarm, we can find out which process set the alarm timer to
>> resume system by below trace log:
>>
>> ......
>> Binder:2976_6-3473 [005] d..2 1076.587732: alarmtimer_start: process:Binder:2976_6
>> alarmtimer type:ALARM_BOOTTIME expires:1234154000000 time: 1970-1-1 0:20:35
>>
>> Binder:2976_7-3480 [002] d..2 1076.592707: alarmtimer_cancel: process:Binder:2976_7
>> alarmtimer type:ALARM_BOOTTIME expires:1325463060000000000 time: 2012-1-2 0:11:0
>>
>> Binder:2976_7-3480 [002] d..2 1076.592731: alarmtimer_start: process:Binder:2976_7
>> alarmtimer type:ALARM_BOOTTIME expires:1325378040000000000 time: 2012-1-1 0:34:0
>>
>> system_server-2976 [003] d..2 1076.605587: alarmtimer_cancel: process:system_server
>> alarmtimer type:ALARM_BOOTTIME expires:1234154000000 time: 1970-1-1 0:20:35
>>
>> system_server-2976 [003] d..2 1076.605608: alarmtimer_start: process:system_server
>> alarmtimer type:ALARM_BOOTTIME expires:1234155000000 time: 1970-1-1 0:20:35
>>
>> system_server-3000 [002] ...1 1087.737565: alarmtimer_suspend: alarmtimer type:ALARM_BOOTTIME
>> expires time: 2012-1-1 0:34:0
>> ......
>>
>> From the trace log, we can find out the 'Binder:2976_7' process set one alarm
>> timer which resumes the system.
>
> Do you have any comments about this patch? Thanks.
No objection from me. I'll queue it for testing.
thanks
-john
next prev parent reply other threads:[~2016-08-30 18:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 4:23 [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer Baolin Wang
2016-08-30 11:50 ` Baolin Wang
2016-08-30 15:42 ` Steven Rostedt
2016-08-31 3:18 ` Baolin Wang
2016-08-30 18:58 ` John Stultz [this message]
2016-08-31 5:29 ` Baolin Wang
2016-10-11 10:48 Baolin Wang
2016-10-17 19:03 ` Steven Rostedt
2016-10-18 2:24 ` Baolin Wang
2016-10-11 10:51 Baolin Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALAqxLXdeQ5snMbCxZRowu_BRDA+DXKLR3YE39tB7NDrAzmpig@mail.gmail.com \
--to=john.stultz@linaro.org \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).