linux-kernel - Re: [PATCH v2 1/4] tracing: Added hardware latency tracer

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: <20160822151615.29b19244@grimm.local.home>
Date:   Mon, 22 Aug 2016 15:16:15 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Nilay Vaish <nilayvaish@...il.com>
Cc:     Linux Kernel list <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Clark Williams <williams@...hat.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Jon Masters <jcm@...hat.com>, Daniel Wagner <wagi@...om.org>,
        Carsten Emde <C.Emde@...dl.org>,
        Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH v2 1/4] tracing: Added hardware latency tracer

On Mon, 22 Aug 2016 12:27:58 -0500
Nilay Vaish <nilayvaish@...il.com> wrote:


> > +static void trace_hwlat_sample(struct hwlat_sample *sample)
> > +{
> > +       struct trace_array *tr = hwlat_trace;
> > +       struct trace_event_call *call = &event_hwlat;  
> 
> Steven, where is this variable event_hwlat declared?  To me it seems
> that some macro is declaring it (most likely DEFINE_EVENT) but I was
> not able to figure out the chain that ends up in the declaration.

Yeah, it's created similarly to how trace_events are created.

It's created via kernel/trace/trace_export.c using
kernel/trace/trace_entries.h

-- Steve