From: Steven Rostedt <rostedt@goodmis.org>
To: Divya Vyas <edivya.vyas@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Subject: Re: Merge ftrace data of host and guest
Date: Sat, 20 Dec 2014 00:10:08 -0500 [thread overview]
Message-ID: <20141220051008.GE5474@home.goodmis.org> (raw)
In-Reply-To: <CAGfiMvCLgdaACWuUJAWecaLP9cSZRLFzzWgNGoiZTidT9m60cg@mail.gmail.com>
On Fri, Dec 19, 2014 at 05:52:52PM +0530, Divya Vyas wrote:
> Hi,
Hi, it would be helpful if you Cc'd me. I would have responded quicker. Luckily,
someone noticed this email and told me about it.
>
> I think it is not desired output . Ths script is written for diffrent
> format .ftrace format is ( trace-cmd report command generates) :
I'm actually working on trace-cmd this week and hopefully I'll be able to release
2.5 by x-mas.
I believe that Masami is going to start continuing work on the virt guest
tracer for trace-cmd.
Also, for now, for a crud way of merging, if both the gettimeofday clocks
of the host and guest are synced, you could do:
guest> trace-cmd record -o guest.dat --date ...
host> trace-cmd record -o host.dat --date ...
and then run:
trace-cmd report -i guest.dat -i host.dat
and trace-cmd will merge the two. The --date will add a way to sync the trace
timestamps to a wall clock and that will be used to try to interleave the
events of both the data files.
-- Steve
next prev parent reply other threads:[~2014-12-20 5:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 12:22 Merge ftrace data of host and guest Divya Vyas
2014-12-20 5:10 ` Steven Rostedt [this message]
2014-12-22 7:04 ` Divya Vyas
2014-12-22 7:07 ` Divya Vyas
2014-12-22 8:33 ` Masami Hiramatsu
[not found] ` <CAGfiMvAALjFU+5FdmXa1VTQM6ZeEAZG5F1VDO60BRx4EK9zMZQ@mail.gmail.com>
[not found] ` <CAGfiMvCQrcwsdDxM5XJtX=BZOF+LbpRJJgLCYEGTRNKkUioK9g@mail.gmail.com>
[not found] ` <CAGfiMvA_K+r=p_G+PJ0SJdTqwZw3NBDtNO0=+we8x6-a6+ugPg@mail.gmail.com>
2015-01-22 10:09 ` Divya Vyas
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=20141220051008.GE5474@home.goodmis.org \
--to=rostedt@goodmis.org \
--cc=edivya.vyas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.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