From: Steven Rostedt <rostedt@goodmis.org>
To: Nilay Vaish <nilayvaish@gmail.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Clark Williams <williams@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jon Masters <jcm@redhat.com>, Daniel Wagner <wagi@monom.org>,
Carsten Emde <C.Emde@osadl.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v2 1/4] tracing: Added hardware latency tracer
Date: Mon, 22 Aug 2016 15:16:15 -0400 [thread overview]
Message-ID: <20160822151615.29b19244@grimm.local.home> (raw)
In-Reply-To: <CACbG308jy3eCxCxfjJqv_hcfUQOE1usRs4N9mkAAaBmhvZkehA@mail.gmail.com>
On Mon, 22 Aug 2016 12:27:58 -0500
Nilay Vaish <nilayvaish@gmail.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
next prev parent reply other threads:[~2016-08-22 19:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 13:53 [PATCH v2 0/4] tracing: Add Hardware Latency detector tracer Steven Rostedt
2016-08-10 13:53 ` [PATCH v2 1/4] tracing: Added hardware latency tracer Steven Rostedt
2016-08-22 17:27 ` Nilay Vaish
2016-08-22 19:16 ` Steven Rostedt [this message]
2016-08-10 13:53 ` [PATCH v2 2/4] tracing: Add documentation for hwlat_detector tracer Steven Rostedt
2016-08-10 13:53 ` [PATCH v2 3/4] tracing: Have hwlat trace migrate across tracing_cpumask CPUs Steven Rostedt
2016-08-10 13:54 ` [PATCH v2 4/4] tracing: Add NMI tracing in hwlat detector Steven Rostedt
2016-08-12 18:13 ` [PATCH v2 0/4] tracing: Add Hardware Latency detector tracer Daniel Bristot de Oliveira
2016-08-19 14:09 ` Peter Zijlstra
2016-08-19 14:26 ` Steven Rostedt
2016-08-19 15:05 ` Peter Zijlstra
2016-08-19 16:36 ` John Stultz
2016-08-23 8:47 ` Peter Zijlstra
2016-08-23 8:48 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160822151615.29b19244@grimm.local.home \
--to=rostedt@goodmis.org \
--cc=C.Emde@osadl.org \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=jcm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nilayvaish@gmail.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=wagi@monom.org \
--cc=williams@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox