From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
To: Jun Koi <junkoi2004@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: kvmtrace?
Date: Mon, 07 Jul 2008 16:07:05 +0200 [thread overview]
Message-ID: <48722309.7020500@linux.vnet.ibm.com> (raw)
In-Reply-To: <fdaac4d50807061744x5bf94973s6f7cc8b8f4c41afb@mail.gmail.com>
Jun Koi wrote:
> Hi,
>
> Could anybody explain a bit about kvmtrace? I cannot find any doc on
> it anywhere.
>
> - Is there any short usage instruction for kvmtrace?
>
I don't know if there is an official doc yet, but you can just start
with the simple version like:
./kvmtrace -o outfile -w 5
which traces for 5 seconds to outfile.*
After that you can cat that file and pipe it to kvmtrace_format which
converts it to a readable file:
cat outfile.kvmtrace.0 | ./kvmtrace_format formats
formats is a simple file defining how to present the trace records.
> - Which kind of data kvmtrace can collect?
>
Due to the structure of the "formats" file (lockated in
kvm-userspace/user/formats) this is also a list of the event types
currently tracked - it is readable ascii and lists event+additional data
reported.
Both kvmtrace (c) & kvmtrace_formats (python) are not very big (yet) so
if you want to go further just look into the code. While I'm sure that
it will grow in complexity in the future it's clearly arranged and easy
to read atm.
> Many thanks,
> Jun
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Grüsse / regards,
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization
next prev parent reply other threads:[~2008-07-07 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 0:44 kvmtrace? Jun Koi
2008-07-07 14:07 ` Christian Ehrhardt [this message]
2008-07-07 15:34 ` kvmtrace? Jun Koi
2008-07-10 10:01 ` kvmtrace? Christian Ehrhardt
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=48722309.7020500@linux.vnet.ibm.com \
--to=ehrhardt@linux.vnet.ibm.com \
--cc=junkoi2004@gmail.com \
--cc=kvm@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