Re: [PATCH v4 3/3] tracing: Histogram for missed timer offsets

[Steven Rostedt]

On Wed, 31 Aug 2016 17:04:54 +0530
Binoy Jayan <binoy.jayan@xxxxxxxxxx> wrote:

> On 30 August 2016 at 19:45, Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:
> > On Tue, 30 Aug 2016 15:58:44 +0530
> > Binoy Jayan <binoy.jayan@xxxxxxxxxx> wrote:
> >  
> >> +
> >> +     TP_STRUCT__entry(
> >> +             __field(long long,      toffset)
> >> +             __array(char,           ccomm,  TASK_COMM_LEN)  
> >
> > Can curr be different than current? If not, lets not record it.
> >
> > -- Steve
> >  
> 
> Hi Steve,
> 
> If my understanding is right, I think both are not the same. The
> predefined field relates to the current
> process which was interrupted by the hrtimer. This I guess does not
> have a meaning in this context.
> Mostly it is the idle process which is interrupted by the hrtimer. But
> the ccomm field refers to the task
> woken up by the process. The latencies are measured for this task. So
> I it is needed.
> 

Then what is tcomm?

-- Steve