From: Steven Rostedt <rostedt@goodmis.org>
To: Tom Zanussi <tom.zanussi@linux.intel.com>
Cc: Daniel Wagner <daniel.wagner@bmw-carit.de>,
Ingo Molnar <mingo@redhat.com>, Carsten Emde <C.Emde@osadl.org>,
linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFD 5/5] tracing: Add trace_irqsoff tracepoints
Date: Thu, 30 Apr 2015 22:54:11 -0400 [thread overview]
Message-ID: <20150430225411.37cbb7cc@grimm.local.home> (raw)
In-Reply-To: <1430446492.17922.32.camel@picadillo>
On Thu, 30 Apr 2015 21:14:52 -0500
Tom Zanussi <tom.zanussi@linux.intel.com> wrote:
> > 'hist:key=latency.bucket:val=hitcount:sort=latency if cpu==0'
> >
> > but I haven't got this working. I didn't spend much time figuring out
> > why this doesn't work. Even if the above is working you still
>
> I think it doesn't work because the tracepoint doesn't actually have a
> 'cpu' field to use in the filter...
Perhaps we should add special fields that don't use the tracepoint
field, but can use generically know fields that are always known when
the tracepoint is triggered. COMM could be one, as well as CPU.
-- Steve
next prev parent reply other threads:[~2015-05-01 2:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 10:06 [RFD 0/5] Add latency histogram Daniel Wagner
2015-04-30 10:06 ` [RFD 1/5] tracing: 'hist' triggers Daniel Wagner
2015-04-30 10:06 ` [RFD 2/5] tracing: Add support to sort on the key Daniel Wagner
2015-05-01 2:02 ` Tom Zanussi
2015-04-30 10:06 ` [RFD 3/5] tracing: Add option to quantize key values Daniel Wagner
2015-05-01 2:12 ` Tom Zanussi
2015-04-30 10:06 ` [RFD 4/5] tracing: Deference pointers without RCU checks Daniel Wagner
2015-04-30 10:06 ` [RFD 5/5] tracing: Add trace_irqsoff tracepoints Daniel Wagner
2015-05-01 2:14 ` Tom Zanussi
2015-05-01 2:54 ` Steven Rostedt [this message]
2015-05-01 9:23 ` Daniel Wagner
2015-05-04 14:05 ` Daniel Wagner
2015-05-04 15:41 ` Daniel Wagner
2015-05-06 6:31 ` Daniel Wagner
2015-05-01 1:52 ` [RFD 0/5] Add latency histogram Tom Zanussi
2015-05-01 9:22 ` Daniel Wagner
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=20150430225411.37cbb7cc@grimm.local.home \
--to=rostedt@goodmis.org \
--cc=C.Emde@osadl.org \
--cc=daniel.wagner@bmw-carit.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tom.zanussi@linux.intel.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;
as well as URLs for NNTP newsgroup(s).