From: Steven Rostedt <rostedt@goodmis.org>
To: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Cc: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>,
linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH 0/2] KernelShark2.0: Use libtracefs APIs to access tracefs
Date: Mon, 9 Mar 2020 11:44:08 -0400 [thread overview]
Message-ID: <20200309114408.14440fff@gandalf.local.home> (raw)
In-Reply-To: <4aab233c-6f5b-59a7-564b-e520ed1f569f@gmail.com>
On Mon, 9 Mar 2020 11:17:44 +0200
"Yordan Karadzhov (VMware)" <y.karadz@gmail.com> wrote:
> > Just confirmed it. If I add kvm events to the guest, it synchronizes
> > automatically. Thus, it's a bug to expect the guest to have kvm events, as
> > there's no reason for them to do so.
>
> Is it possible that something else gets enabled during the recording of
> the data, that actually makes the difference?
> Y.
Unfortunately, I blew away the files with the issue and tried to reproduce
it, and I can't :-/
Now even without the kvm events it appears to work. I may try one more
thing (which is to rebuild the guest without KVM at all), and see if I can
bring back the issue. But for now, I guess it's a "WORKS FOR ME" :-/
-- Steve
next prev parent reply other threads:[~2020-03-09 15:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 9:29 [PATCH 0/2] KernelShark2.0: Use libtracefs APIs to access tracefs Tzvetomir Stoyanov (VMware)
2020-03-06 9:29 ` [PATCH 1/2] KernelShark2.0: Link KernelShark to libtracefs Tzvetomir Stoyanov (VMware)
2020-03-06 9:29 ` [PATCH 2/2] KernelShark2.0: Use libtracefs APIs to access tracefs Tzvetomir Stoyanov (VMware)
2020-03-06 20:13 ` [PATCH 0/2] " Steven Rostedt
2020-03-06 22:34 ` Steven Rostedt
2020-03-09 9:17 ` Yordan Karadzhov (VMware)
2020-03-09 15:44 ` Steven Rostedt [this message]
2020-03-09 16:30 ` Steven Rostedt
2020-03-09 9:10 ` Yordan Karadzhov (VMware)
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=20200309114408.14440fff@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tz.stoyanov@gmail.com \
--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 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).