Linux-Trace-Devel Archive on
 help / color / Atom feed
From: "Yordan Karadzhov (VMware)" <>
To: Steven Rostedt <>,
	"Tzvetomir Stoyanov (VMware)" <>
Subject: Re: [PATCH 0/2] KernelShark2.0: Use libtracefs APIs to access tracefs
Date: Mon, 9 Mar 2020 11:17:44 +0200
Message-ID: <> (raw)
In-Reply-To: <20200306173411.783cccd0@gandalf.local.home>

On 7.03.20 г. 0:34 ч., Steven Rostedt wrote:
> On Fri, 6 Mar 2020 15:13:56 -0500
> Steven Rostedt <> wrote:
>> On Fri,  6 Mar 2020 11:29:00 +0200
>> "Tzvetomir Stoyanov (VMware)" <> wrote:
>>> From: "Tzvetomir (VMware)  Stoyanov" <>
>>> The tracefs library provides APIs for accessing files from tracefs.
>>> The library is part of trace-cmd, it is installed as part of trace-cmd
>>> installation. KernelShark uses some of those APIs and must be linked with
>>> the library
>>> Tzvetomir (VMware)  Stoyanov (2):
>>>    KernelShark2.0: Link KernelShark to libtracefs
>>>    KernelShark2.0: Use libtracefs APIs to access tracefs
>> I added these patches to the latest kernelshark-2.0 and it still doesn't
>> work for me. I did a little debugging, and noticed that it fails while
>> reading the guest trace.dat file with:
>> plugin "kvm_combo" failed to initialize on stream /tmp/trace-host-Fedora21.
>> It seems to require that the guest trace.dat file has kvm events?
>> Note, as I build my guest kernel with a make localmodconfig, which disables
>> all modules that are not necessary to boot the box, there is no kvm events
>> there. I can see why the host may need them, but not the guest. I'll
>> rebuild my guest kernel with kvm events and see if that solves this (but
>> that shouldn't be the case).
> 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?

> -- Steve

  reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-06  9:29 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) [this message]
2020-03-09 15:44       ` Steven Rostedt
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Trace-Devel Archive on

Archives are clonable:
	git clone --mirror linux-trace-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-trace-devel linux-trace-devel/ \
	public-inbox-index linux-trace-devel

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone