All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dfaggioli@suse.com>
To: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org
Subject: Accuracy of traces sync [Was: Re: [PATCH] Fix `make -jN trace-cmd gui`]
Date: Fri, 20 Nov 2020 14:43:21 +0100	[thread overview]
Message-ID: <849f846631f3014c3eff7f37a7d61493e2af66a9.camel@suse.com> (raw)
In-Reply-To: <02672da2-8b62-a573-786d-1cb8f5970e85@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2004 bytes --]

On Fri, 2020-11-20 at 14:32 +0200, Yordan Karadzhov (VMware) wrote:
> On 20.11.20 г. 14:06 ч., Dario Faggioli wrote:
> > > 
> > Yep, sure! I followed the talks you've been giving about it at
> > events, and I even played a little with what you have here:
> > 
> > https://github.com/yordan-karadzhov/kernel-shark-2.alpha
> > 
> > The host-guest tracing part, as I think you can guess.
> 
> Ciao Dario,
>
Hey!

> I am very happy to hear that. The timestamp synchronization patches
> for 
> trace-cmd are almost ready to go upstream.
> 
Yes, I tried those patches!

In fact, now that I have you here, do you mind if I change the subject
and ask a quick question about them?

So, you often say that "the accuracy of the synchronization protocol is
XX ms". Now, I guess that means that an event in the guest and the
corresponding event in the host (or vice versa) are XX ms apart. And
that's even after the synchronization of the two traces, is that right?

Question is, how do you measure that? Sure, I can look manually for an
occurrence of the pattern that I described above: i.e., an event in the
guest, then the corresponding one in the host and compute the
difference between the timestamps.

But do you have a way to do so automatically, or with a script/program,
etc?

I saw that the series included a patch which was meant at debugging and
profiling PTP, but even with that one applied and having it generate
the graphs, I have not been able to get that info without manual
inspection.

> And we are currently reviewing a beta version of KernelShark_2 that
> will 
> include the guest/host visualization.
> As Steven said: stay tuned!
> 
You bet I will. :-P

Thanks and Regards
-- 
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-11-20 13:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17 21:16 [PATCH] Fix `make -jN trace-cmd gui` Dario Faggioli
2020-11-20  3:09 ` Steven Rostedt
2020-11-20 12:06   ` Dario Faggioli
2020-11-20 12:32     ` Yordan Karadzhov (VMware)
2020-11-20 13:43       ` Dario Faggioli [this message]
2020-11-20 14:08         ` Accuracy of traces sync [Was: Re: [PATCH] Fix `make -jN trace-cmd gui`] Steven Rostedt
2020-11-26  0:15           ` Dario Faggioli
2020-11-26  3:53             ` Tzvetomir Stoyanov

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=849f846631f3014c3eff7f37a7d61493e2af66a9.camel@suse.com \
    --to=dfaggioli@suse.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=y.karadz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.