From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932171AbcHRCVR (ORCPT ); Wed, 17 Aug 2016 22:21:17 -0400 Received: from mail-yw0-f181.google.com ([209.85.161.181]:35154 "EHLO mail-yw0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753480AbcHRCVQ (ORCPT ); Wed, 17 Aug 2016 22:21:16 -0400 MIME-Version: 1.0 In-Reply-To: References: <787c0df77330b8e33280a06fdde6754752fa79db.1470992599.git.baolin.wang@linaro.org> From: Baolin Wang Date: Thu, 18 Aug 2016 10:21:15 +0800 Message-ID: Subject: Re: [PATCH] time: alarmtimer: Add the trcepoints for alarmtimer To: John Stultz Cc: Steven Rostedt , Ingo Molnar , Thomas Gleixner , Mark Brown , lkml Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi John, On 18 August 2016 at 04:00, John Stultz wrote: > On Fri, Aug 12, 2016 at 2:16 AM, Baolin Wang 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 > > > 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