From: Jan Kiszka <jan.kiszka@web.de>
To: Manish Regmi <regmi.manish@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: kvmtrace and debugging kvm
Date: Wed, 14 Apr 2010 09:56:15 +0200 [thread overview]
Message-ID: <4BC5751F.9080403@web.de> (raw)
In-Reply-To: <w2x652016d31004132011i271b86c5x84f43d415d645ed1@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
Manish Regmi wrote:
> hi,
> I am trying to use kvmtrace but it looks like its no longer used. in
Right, kernel support was removed a few releases ago. I think it's time
to drop that tool from the qemu-kvm package.
> kvm_main.c it is returning -EOPNOTSUP.
> kvmtrace -V -D test -o mykvmtest
> does not seem to do anything.
>
> is it no longer used? is there any better way of debugging kvm?
Use ftrace. KVM comes with an even better level of event trace
instrumentation for that framework than it was the case with kvmtrace.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
prev parent reply other threads:[~2010-04-14 7:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 3:11 kvmtrace and debugging kvm Manish Regmi
2010-04-14 7:56 ` Jan Kiszka [this message]
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=4BC5751F.9080403@web.de \
--to=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=regmi.manish@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox