[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMz4kuJLfC=3ZK7POOcq9tgYdk0e5veS4S75PfRJ07qhzgr9JA@mail.gmail.com>
Date: Thu, 18 Aug 2016 10:21:15 +0800
From: Baolin Wang <baolin.wang@...aro.org>
To: John Stultz <john.stultz@...aro.org>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Mark Brown <broonie@...nel.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] time: alarmtimer: Add the trcepoints for alarmtimer
Hi John,
On 18 August 2016 at 04:00, John Stultz <john.stultz@...aro.org> wrote:
> On Fri, Aug 12, 2016 at 2:16 AM, Baolin Wang <baolin.wang@...aro.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.
>>
>> Signed-off-by: Baolin Wang <baolin.wang@...aro.org>
>
>
> Looks reasonable to me. Might be good to get a specific example of
> something you've used this for (with example output) in the commit
> log.
OK. Will add one example with the trace log in next version.
>
> Please also fix up the kbuild test issues and resubmit.
OK. Thanks.
>
> thanks
> -john
--
Baolin.wang
Best Regards
Powered by blists - more mailing lists