From: David Ahern <dsahern@gmail.com>
To: Jiri Olsa <jolsa@kernel.org>, linux-kernel@vger.kernel.org
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jeremie Galarneau <jgalar@efficios.com>,
Namhyung Kim <namhyung@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Tom Zanussi <tzanussi@gmail.com>
Subject: Re: [PATCH 4/8] perf data: Add a 'perf' prefix to the generic fields
Date: Thu, 11 Dec 2014 11:55:06 -0700 [thread overview]
Message-ID: <5489E88A.3000801@gmail.com> (raw)
In-Reply-To: <1418310749-22267-5-git-send-email-jolsa@kernel.org>
On 12/11/14 8:12 AM, Jiri Olsa wrote:
> Before:
> $ babeltrace ./ctf-data/
> [03:19:13.962131936] (+0.000001935) cycles: { }, { ip = 0xFFFFFFFF8105443A, tid = 20714, pid = 20714, period = 8 }
> [03:19:13.962133732] (+0.000001796) cycles: { }, { ip = 0xFFFFFFFF8105443A, tid = 20714, pid = 20714, period = 114 }
> ...
>
> Now:
> $ babeltrace ./ctf-data/
> [03:19:13.962131936] (+0.000001935) cycles: { }, { perf_ip = 0xFFFFFFFF8105443A, perf_tid = 20714, perf_pid = 20714, perf_period = 8 }
> [03:19:13.962133732] (+0.000001796) cycles: { }, { perf_ip = 0xFFFFFFFF8105443A, perf_tid = 20714, perf_pid = 20714, perf_period = 114 }
> ...
How is babeltrace showing time-of-day for perf-based data files? Is that
tod when the command is run?
David
next prev parent reply other threads:[~2014-12-11 18:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 15:12 [PATCHv2 0/8] perf tools: Add perf data CTF conversion Jiri Olsa
2014-12-11 15:12 ` [PATCH 1/8] perf tools: Add feature check for libbabeltrace Jiri Olsa
2014-12-11 15:12 ` [PATCH 2/8] perf tools: Add new perf data command Jiri Olsa
2014-12-11 15:12 ` [PATCH 3/8] perf data: Add perf data to CTF conversion support Jiri Olsa
2014-12-11 17:06 ` David Ahern
2014-12-11 17:15 ` Jiri Olsa
2014-12-11 15:12 ` [PATCH 4/8] perf data: Add a 'perf' prefix to the generic fields Jiri Olsa
2014-12-11 18:55 ` David Ahern [this message]
2014-12-11 18:57 ` Sebastian Andrzej Siewior
2014-12-11 19:47 ` David Ahern
2014-12-11 20:22 ` Sebastian Andrzej Siewior
2014-12-11 15:12 ` [PATCH 5/8] perf data: Add tracepoint events fields CTF conversion support Jiri Olsa
2014-12-11 15:12 ` [PATCH 6/8] perf data: Switch to multiple cpu stream files Jiri Olsa
2014-12-11 15:12 ` [PATCH 7/8] perf data: Enable stream flush within processing Jiri Olsa
2014-12-11 15:12 ` [PATCH 8/8] perf data: Add support for setting ordered_events queue size Jiri Olsa
2014-12-22 15:08 ` [PATCHv2 0/8] perf tools: Add perf data CTF conversion Jiri Olsa
2015-01-08 10:28 ` Jiri Olsa
2015-01-08 13:52 ` Namhyung Kim
2015-01-09 10:38 ` Jiri Olsa
2015-01-08 14:29 ` Peter Zijlstra
2015-01-08 14:38 ` Jiri Olsa
2015-01-09 9:58 ` Peter Zijlstra
2015-01-09 10:03 ` Jiri Olsa
-- strict thread matches above, loose matches on Subject: below --
2015-01-15 16:15 [PATCHv3 " Jiri Olsa
2015-01-15 16:15 ` [PATCH 4/8] perf data: Add a 'perf' prefix to the generic fields Jiri Olsa
2014-12-03 16:23 [PATCH 0/8] perf tools: Add perf data CTF conversion Jiri Olsa
2014-12-03 16:23 ` [PATCH 4/8] perf data: Add a 'perf' prefix to the generic fields Jiri Olsa
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=5489E88A.3000801@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=fweisbec@gmail.com \
--cc=jgalar@efficios.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=tzanussi@gmail.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