From: Jan Kiszka <jan.kiszka@web.de>
To: David Ahern <dsahern@gmail.com>
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 23:07:23 +0200 [thread overview]
Message-ID: <4D9F790B.2000300@web.de> (raw)
In-Reply-To: <4D9F59AC.6080707@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 324 bytes --]
On 2011-04-08 20:53, David Ahern wrote:
> 2.6.38.2 kernel with trace-cmd git pulled this morning:
>
> trace-cmd record -e kvm
>
> trace-cmd report 2>&1 | less
>
> trace-cmd: No such file or directory
Does this error come from trace-cmd failing to find its kvm plugin?
Check what strace -e open says.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2011-04-08 21:07 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 [this message]
2011-04-08 21:12 ` David Ahern
2011-04-08 21:18 ` Jan Kiszka
2011-04-08 23:26 ` David Ahern
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=4D9F790B.2000300@web.de \
--to=jan.kiszka@web.de \
--cc=dsahern@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox