From: Steven Rostedt <rostedt@goodmis.org>
To: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
Cc: Stefano De Venuto <stefano.devenuto99@gmail.com>,
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: Mon, 22 Mar 2021 10:56:24 -0400 [thread overview]
Message-ID: <20210322105624.40aa27b1@gandalf.local.home> (raw)
In-Reply-To: <CAPpZLN7ChRzU1b2t1KSbT+MB0An=CJJxnDizaO41K=XSz8sb6g@mail.gmail.com>
On Mon, 22 Mar 2021 12:13:09 +0200
Tzvetomir Stoyanov <tz.stoyanov@gmail.com> wrote:
> Confirmed, the problem is in the trace-cmd logic that works with the
> KVM scaling. Looks like tsc-scaling-ratio is the default KVM scaling
> on your machine, (1 << 32), and in that case the scaling should be
> ignored in our calculations. I still have no solution, going to
> analyze how the KVM scaling works.
I'm guessing that this was run on a AMD CPU, as the default scaling (the
one to ignore) is 1 << 32 for AMD and for Intel it's 1 << 48.
-- Steve
next prev parent reply other threads:[~2021-03-22 14:57 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
[not found] ` <0f6e158c-43a3-4117-2a17-5a13cd6a7970@gmail.com>
2021-03-22 10:13 ` Tzvetomir Stoyanov
2021-03-22 14:56 ` Steven Rostedt [this message]
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=20210322105624.40aa27b1@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=dfaggioli@suse.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=stefano.devenuto99@gmail.com \
--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).