linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
To: Stefano De Venuto <stefano.devenuto99@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
	Dario Faggioli <dfaggioli@suse.com>
Subject: Re: [PATCH v32 0/5]Timestamp synchronization of host - guest tracing session
Date: Sat, 20 Mar 2021 08:25:48 +0200	[thread overview]
Message-ID: <CAPpZLN4yn2qn7uqNLqkxdnHfM_5SdtkjPY41atY5m-FPG3rudA@mail.gmail.com> (raw)
In-Reply-To: <80486620-fe8f-49a5-cdac-05bb2b969984@gmail.com>

Hi Stefano,

On Fri, Mar 19, 2021 at 7:44 PM Stefano De Venuto
<stefano.devenuto99@gmail.com> wrote:
>
>
>
> On 3/19/21 12:55 PM, Tzvetomir Stoyanov wrote:
> > Hi Stefano,
> >
> > On Fri, Mar 19, 2021 at 12:08 PM Stefano De Venuto
> > <stefano.devenuto99@gmail.com> wrote:
> Hi!
> >> The commands used to record are:
> >>
> >> Host:
> >> # trace-cmd record -C x86-tsc -e kvm:* -e msr:* -A tumbleweed:823 -e
> >> msr:* -C x86-tsc sleep 1
> > The guest trace clock is set automatically as the host, so this
> > command should be enough:
> > # trace-cmd record -C x86-tsc -e kvm:* -e msr:* -A tumbleweed:823 -e
> > msr:*  sleep 1
> >
> >> Guest:
> >> # echo x86-tsc > /sys/kernel/tracing/trace_clock
> > There is no need to set manually the guest clock, it will be
> > overwritten by trace-cmd agent.
> >
> Thanks so much for the proper way to do it, really appreciated.
> >> If necessary, I can provide more info about my setup, or do more tests.
> > Yes, please can you send me both host and guest trace files ?
> Here are the trace files, host and guest respectively:
>
> - http://xenbits.xen.org/people/dariof/tracing-examples/kvm/sync-kvmclock/trace.dat
> - http://xenbits.xen.org/people/dariof/tracing-examples/kvm/sync-kvmclock/trace-tumbleweed.dat
>
> > Also, it will be useful to send me the content of the KVM debug files:
> >     /sys/kernel/debug/kvm/<guest ID>/vcpu<*>/tsc-offset
> The guest has one vcpu (vcpu0) and the content of the file is:
>
> 255647917761327

Looks like there is a scaling between host and guest clocks in your
setup, not just a simple offset. We did not test yet our
implementation with scaling, although both offset and scaling are part
of the calculations. That makes your use case very valuable for us, as
we have an opportunity to test it now. And yes, looks like we have a
bug here.
Please, when you have time, can you repeat again the tracing session
and send again both trace files + the content of the KVM debug files:
     /sys/kernel/debug/kvm/<guest ID>/vcpu0/tsc-offset
     /sys/kernel/debug/kvm/<guest ID>/vcpu0/tsc-scaling-ratio
I'm asking to do a new trace, as most probably these offset and
scaling could be different now.

Thanks!

> >>
> >> Thanks and Regards,
> >>
> >> Stefano
> > Thanks for testing this code!
> >
> Thanks for your time,
>
> Stefano



-- 
Tzvetomir (Ceco) Stoyanov
VMware Open Source Technology Center

  reply	other threads:[~2021-03-20 11:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15  6:18 [PATCH v32 0/5]Timestamp synchronization of host - guest tracing session Tzvetomir Stoyanov (VMware)
2021-03-15  6:18 ` [PATCH v32 1/5] trace-cmd: Add dummy function to initialize timestamp sync logic Tzvetomir Stoyanov (VMware)
2021-03-15  6:18 ` [PATCH v32 2/5] trace-cmd: Add timestamp synchronization per vCPU Tzvetomir Stoyanov (VMware)
2021-03-15  6:18 ` [PATCH v32 3/5] trace-cmd: PTP-like algorithm for host - guest timestamp synchronization Tzvetomir Stoyanov (VMware)
2021-03-15  6:18 ` [PATCH v32 4/5] trace-cmd: Debug scripts for " Tzvetomir Stoyanov (VMware)
2021-03-15  6:18 ` [PATCH v32 5/5] trace-cmd [POC]: Add KVM timestamp synchronization plugin Tzvetomir Stoyanov (VMware)
2021-03-19 10:08 ` [PATCH v32 0/5]Timestamp synchronization of host - guest tracing session Stefano De Venuto
2021-03-19 11:55   ` Tzvetomir Stoyanov
2021-03-19 17:44     ` Stefano De Venuto
2021-03-20  6:25       ` Tzvetomir Stoyanov [this message]
     [not found]         ` <0f6e158c-43a3-4117-2a17-5a13cd6a7970@gmail.com>
2021-03-22 10:13           ` Tzvetomir Stoyanov
2021-03-22 14:56             ` Steven Rostedt
2021-03-25 20:55               ` Dario Faggioli
2021-03-25  7:20           ` Tzvetomir Stoyanov
2021-03-25 18:01             ` Stefano De Venuto

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=CAPpZLN4yn2qn7uqNLqkxdnHfM_5SdtkjPY41atY5m-FPG3rudA@mail.gmail.com \
    --to=tz.stoyanov@gmail.com \
    --cc=dfaggioli@suse.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=stefano.devenuto99@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;
as well as URLs for NNTP newsgroup(s).