All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dfaggioli@suse.com>
To: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>,
	Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: Re: Kernelshark v2 all-black plots area
Date: Tue, 09 Feb 2021 17:13:09 +0100	[thread overview]
Message-ID: <e07be2e367576882d0cf84c33834ecafaba38136.camel@suse.com> (raw)
In-Reply-To: <ce06b82f-6335-4653-0d27-e48a37ffb5aa@gmail.com>

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

On Tue, 2021-02-09 at 15:06 +0200, Yordan Karadzhov (VMware) wrote:
> Ciao Dario,
> 
Ciao! :-)

> There is a bug in one of the patches from the last patch-set I sent. 
> This bug was reported by Tzvetomir. My guess is that you are hitting
> the 
> same issue. If this is the case you must also have an error message 
> saying "Unable to find FreeSans font".
> 
Yep, I was seeing that too. And, TBH, for a while I installed font
packages like mad, thinking it was related to something like that. :-P

> You can manually do the fix suggested by Tzvetomir (see his reply to 
> [PATCH 15/24] kernel-shark: Update KsDualMarker and KsGLWidget) or
> just 
> get a corrected (rebased) version of the code from
> https://github.com/yordan-karadzhov/kernel-shark-v2.beta
> 
Ah, great! I updated (rebase included), and now plots are back.

> Please let me know if this fixes your issue.
>
Indeed it does, thanks a lot again.

Now, if I try "KVM Combo Plot":
- I still see super weird results if I use the KVM clock from last
  patch in Tzvetomir series (but I guess I'll report it there).
- If I use PTP, that kind of works.

If I trace a `sleep 1` on the host, the result is like this:

http://xenbits.xen.org/people/dariof/kernelshark-v2-ptp.png

So, there is ~ 1 sec of data from the guest, coming from trace-cmd
agent. The host, however, went on and traced a little bit longer, even
after closing the connection. It's not too terrible, I'm just curious
whether this is known or it's something weird and it's only me seeing
it.

Evaluating the correctness and the accuracy of the synchronization is a
little bit of a challenge, especially for me that I'm not used to it.
And, at least in part, because I still don't have this change in the
kernel I'm using right now, so some kvm_entry trace points are not
recorded, which means it's tricky pairing VMEntries and VMExits:

https://lore.kernel.org/lkml/160873470698.11652.13483635328769030605.stgit@Wayrath/

It should come with 5.11, but I think I'll quickly apply it to the 5.10
that I'm running, to try to understand better hat's going on.

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:[~2021-02-09 16:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09 10:48 Kernelshark v2 all-black plots area Dario Faggioli
2021-02-09 13:06 ` Yordan Karadzhov (VMware)
2021-02-09 16:13   ` Dario Faggioli [this message]
2021-02-10 11:21     ` Yordan Karadzhov (VMware)
2021-02-10 14:51       ` Dario Faggioli
2021-02-10 15:47         ` Yordan Karadzhov (VMware)
2021-02-10 16:15           ` Dario Faggioli
2021-02-10 16:23           ` Steven Rostedt
2022-04-20  0:38   ` Solomon Tan
2022-04-20  8:06     ` Yordan Karadzhov
2022-04-20 15:17       ` Solomon Tan
2022-04-20 15:38         ` [PATCH 1/2] kernel-shark: Make FreeSans a compulsory component Solomon Tan
2022-04-20 15:38           ` [PATCH 2/2] kernel-shark: Allow FreeSans otf in addition to ttf Solomon Tan
2022-04-21 12:16             ` Yordan Karadzhov
2022-04-21 12:04           ` [PATCH 1/2] kernel-shark: Make FreeSans a compulsory component Yordan Karadzhov

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=e07be2e367576882d0cf84c33834ecafaba38136.camel@suse.com \
    --to=dfaggioli@suse.com \
    --cc=linux-trace-devel@vger.kernel.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.