Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

On 18 October 2016 at 03:03, Steven Rostedt wrote: > On Tue, 11 Oct 2016 18:48:16 +0800 > Baolin Wang wrote: > >> --- >> Changes since v2: >> - Save time as s64 type. >> - Remove 'process_name' parameter and add 'now' parameter. >> - Rename the

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

On 18 October 2016 at 03:03, Steven Rostedt wrote: > On Tue, 11 Oct 2016 18:48:16 +0800 > Baolin Wang wrote: > >> --- >> Changes since v2: >> - Save time as s64 type. >> - Remove 'process_name' parameter and add 'now' parameter. >> - Rename the trace event name. >> - Remove restart trace

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

On Tue, 11 Oct 2016 18:48:16 +0800 Baolin Wang wrote: > For system debugging, we sometimes 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.

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

On Tue, 11 Oct 2016 18:48:16 +0800 Baolin Wang wrote: > For system debugging, we sometimes 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

[PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

For system debugging, we sometimes 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

[PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

For system debugging, we sometimes 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

[PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

For system debugging, we sometimes 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

[PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

For system debugging, we sometimes 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

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

On 31 August 2016 at 02:58, John Stultz wrote: > On Tue, Aug 30, 2016 at 4:50 AM, Baolin Wang wrote: >> Hi, >> >> On 22 August 2016 at 12:23, Baolin Wang wrote: >>> For system debugging, we usually want to know who sets one

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

On 31 August 2016 at 02:58, John Stultz wrote: > On Tue, Aug 30, 2016 at 4:50 AM, Baolin Wang wrote: >> Hi, >> >> On 22 August 2016 at 12:23, 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

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

Hi Steven, On 30 August 2016 at 23:42, Steven Rostedt wrote: > On Tue, 30 Aug 2016 19:50:20 +0800 > Baolin Wang wrote: > >> Hi, >> >> On 22 August 2016 at 12:23, Baolin Wang wrote: >> > For system debugging, we usually want

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

Hi Steven, On 30 August 2016 at 23:42, Steven Rostedt wrote: > On Tue, 30 Aug 2016 19:50:20 +0800 > Baolin Wang wrote: > >> Hi, >> >> On 22 August 2016 at 12:23, Baolin Wang wrote: >> > For system debugging, we usually want to know who sets one alarm timer, the >> > time of the timer, when the

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

On Tue, Aug 30, 2016 at 4:50 AM, Baolin Wang wrote: > Hi, > > On 22 August 2016 at 12:23, 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

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

On Tue, Aug 30, 2016 at 4:50 AM, Baolin Wang wrote: > Hi, > > On 22 August 2016 at 12:23, 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

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

On Tue, 30 Aug 2016 19:50:20 +0800 Baolin Wang wrote: > Hi, > > On 22 August 2016 at 12:23, 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

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

On Tue, 30 Aug 2016 19:50:20 +0800 Baolin Wang wrote: > Hi, > > On 22 August 2016 at 12:23, 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

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

Hi, On 22 August 2016 at 12:23, 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. > >

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

Hi, On 22 August 2016 at 12:23, 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. > > For example, when we debug

[PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

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

[PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

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