linux-kernel - Re: [PATCH] time: alarmtimer: Add the trcepoints for alarmtimer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CALAqxLXQJ0z-G8CyBptupGmDsMEBUf21n-yKyriwhKCqc0omtw@mail.gmail.com>
Date:	Wed, 17 Aug 2016 13:00:00 -0700
From:	John Stultz <john.stultz@...aro.org>
To:	Baolin Wang <baolin.wang@...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

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.

Please also fix up the kbuild test issues and resubmit.

thanks
-john