linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefano De Venuto <stefano.devenuto99@gmail.com>
To: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>,
	rostedt@goodmis.org
Cc: 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: Fri, 19 Mar 2021 11:08:45 +0100	[thread overview]
Message-ID: <6796a75b-6a59-767f-08ec-ee0cbfd8c825@gmail.com> (raw)
In-Reply-To: <20210315061857.168570-1-tz.stoyanov@gmail.com>

Hello,

On 3/15/21 7:18 AM, Tzvetomir Stoyanov (VMware) wrote:
> Basic infrastructure for host - guest timestamp synchronization and a
> PoC implementation of PTP-like and KVM algorithms. 
I'm trying to make some analysis on traces generated by host and guest,
so I applied this series and the related dependencies.

However, when the KVM algorithm is used, the merging process
of the two traces doesn't seem to happen properly.

The output of `trace-cmd report -i trace.dat -i trace-tumbleweed.dat` is:

           trace.dat: cpus=4
trace-tumbleweed.dat: cpus=1
           trace.dat:            sleep-23948 [002]61124758463654:
write_msr:            c0000100, value 7f35092875c0
           trace.dat:           <idle>-0     [000]61124760841508:
write_msr:            c0000100, value 7f6136b75640
           trace.dat:        CPU 0/KVM-1640  [000]61124760851620:
write_msr:            c0011020, value 40000000000000
           trace.dat:        CPU 0/KVM-1640  [000]61124760861778:
read_msr:             c0000101, value ffff9b1b76c00000
           trace.dat:        CPU 0/KVM-1640  [000]61124760862832:
read_msr:             c0000081, value 23001000000000
           trace.dat:        CPU 0/KVM-1640  [000]61124760864347:
read_msr:             c0000082, value ffffffffb5400010
           trace.dat:        CPU 0/KVM-1640  [000]61124760865225:
read_msr:             c0000083, value ffffffffb5401670
           .
           .
           .
trace-tumbleweed.dat:   IPC I/O Parent-4313 [000]8446232460209009653:
write_msr:            c0000100, value 7f94535c7640
trace-tumbleweed.dat:    IPC I/O Child-4503 [000]8446348845232796661:
write_msr:            c001011f, value 4
trace-tumbleweed.dat:    IPC I/O Child-4503 [000]8447532508154803189:
write_msr:            c0000100, value 7f945e8d5780
trace-tumbleweed.dat:           <idle>-0    [000]8452336523564659701:
write_msr:            c001011f, value 0
trace-tumbleweed.dat:           <idle>-0    [000]8452515224268944373:
write_msr:            6e0, value 731478a3bf62
trace-tumbleweed.dat:           <idle>-0    [000]8452610851715789813:
write_msr:            6e0, value 731478968f37
trace-tumbleweed.dat:           <idle>-0    [000]8555757214338495477:
write_msr:            6e0, value 731478853ec1
trace-tumbleweed.dat:           <idle>-0    [000]8555904475882173429:
write_msr:            6e0, value 7314778a60e8
trace-tumbleweed.dat:      kworker/0:1-7351 [000]8556355589182174197:
write_msr:            c0000100, value 7f8373573740

The TimeShift information is inside the guest trace file,
so I think this is not a transfer problem.

I also tried to remove the last patch, the one related to the KVM clock,
in order to use PTP and the two traces are merged correctly.

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

Guest:
# echo x86-tsc > /sys/kernel/tracing/trace_clock
# trace-cmd agent

Am I doing something wrong?

If necessary, I can provide more info about my setup, or do more tests.


Thanks and Regards,

Stefano

  parent reply	other threads:[~2021-03-19 10:09 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 ` Stefano De Venuto [this message]
2021-03-19 11:55   ` [PATCH v32 0/5]Timestamp synchronization of host - guest tracing session Tzvetomir Stoyanov
2021-03-19 17:44     ` Stefano De Venuto
2021-03-20  6:25       ` Tzvetomir Stoyanov
     [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=6796a75b-6a59-767f-08ec-ee0cbfd8c825@gmail.com \
    --to=stefano.devenuto99@gmail.com \
    --cc=dfaggioli@suse.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tz.stoyanov@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).