Linux-Trace-Devel Archive on lore.kernel.org
 help / color / Atom feed
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 12:30:09 -0400
Message-ID: <20200309123009.3cbc6401@gandalf.local.home> (raw)
In-Reply-To: <20200309114408.14440fff@gandalf.local.home>

On Mon, 9 Mar 2020 11:44:08 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> 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" :-/

I still can't reproduce my original issue. Perhaps I did something wrong.
So I guess we can ignore this.

One thing I did notice when testing this, the "all" selection of the KVM
combo plots doesn't seem to work. I have to select each VCPU individually.
Do you see that too?

-- 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)
2020-03-09 15:44       ` Steven Rostedt
2020-03-09 16:30         ` Steven Rostedt [this message]
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=20200309123009.3cbc6401@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

Linux-Trace-Devel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-trace-devel/0 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/ https://lore.kernel.org/linux-trace-devel \
		linux-trace-devel@vger.kernel.org
	public-inbox-index linux-trace-devel

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-trace-devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git