All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	KVM mailing list <kvm@vger.kernel.org>
Subject: Re: trace-cmd errors on kvm events
Date: Fri, 08 Apr 2011 17:26:34 -0600	[thread overview]
Message-ID: <4D9F99AA.8060803@gmail.com> (raw)
In-Reply-To: <4D9F7BC0.8010003@web.de>

On 04/08/11 15:18, Jan Kiszka wrote:
> Let me check... indeed, I'm getting the same file-not-found here with
> trace-cmd.git 9cce1c9b5b when starting it directly from its build directory.
> 
> But maybe your trace-cmd or kernel versions are too old / incompatible.
> I'm not getting complaints about unparseable events with the above
> snapshot and 2.6.38.

2.6.38.2 kernel, trace-cmd 3e8b5b8 which is March 18 (though git pull
done this morning).

For grins I checked-out 9cce1c9b5b and same error:
trace-cmd record -e kvm -- sleep 1
trace-cmd report 2>&1  | less

You do have to put stderr onto stdout to see the messages I reported
earlier. Or look for [FAILED TO PARSE] on the kvm_exit and
kvm_emulate_insn lines.

David


  reply	other threads:[~2011-04-08 23:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08 18:53 trace-cmd errors on kvm events David Ahern
2011-04-08 20:50 ` Stefan Hajnoczi
2011-04-08 20:59   ` David Ahern
2011-04-08 21:07 ` Jan Kiszka
2011-04-08 21:12   ` David Ahern
2011-04-08 21:18     ` Jan Kiszka
2011-04-08 23:26       ` David Ahern [this message]
2011-04-08 23:42         ` Jan Kiszka
2011-04-08 23:58           ` David Ahern
2011-04-21 21:37   ` Steven Rostedt

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=4D9F99AA.8060803@gmail.com \
    --to=dsahern@gmail.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.