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

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: <20160831084246.52d0b47e@gandalf.local.home>
Date:   Wed, 31 Aug 2016 08:42:46 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Binoy Jayan <binoy.jayan@...aro.org>
Cc:     Ingo Molnar <mingo@...hat.com>,
        Daniel Wagner <daniel.wagner@...-carit.de>,
        Arnd Bergmann <arnd@...db.de>,
        Linux kernel mailing list <linux-kernel@...r.kernel.org>,
        Masami <masami.hiramatsu@...aro.org>
Subject: Re: [PATCH v4 3/3] tracing: Histogram for missed timer offsets

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

> On 30 August 2016 at 19:45, Steven Rostedt <rostedt@...dmis.org> wrote:
> > On Tue, 30 Aug 2016 15:58:44 +0530
> > Binoy Jayan <binoy.jayan@...aro.org> 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