From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH] kvm: add flightrecorder script
Date: Mon, 12 Mar 2012 14:48:31 +0000 [thread overview]
Message-ID: <20120312144831.GA32737@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <4F5DE72A.1000103@redhat.com>
On Mon, Mar 12, 2012 at 02:08:10PM +0200, Avi Kivity wrote:
> On 03/09/2012 04:13 PM, Stefan Hajnoczi wrote:
> > The kvm kernel module includes a number of trace events which can be
> > useful when debugging system behavior. Even on production systems these
> > trace events can be used to observe guest behavior and identify the
> > source of problems.
> >
> > The kvm_flightrecorder script is a command-line wrapper for the
> > /sys/kernel/debug/tracing interface. Kernel symbols do not need to be
> > installed.
> >
> > This script captures a fixed-size buffer of KVM trace events. Recent
> > events overwrite the oldest events when the buffer size is exceeded and
> > it is possible to leave KVM tracing enabled for any period of time with
> > just a fixed-size buffer. If the buffer is large enough this script is
> > a useful tool for collecting detailed information after an issue occurs
> > with a guest. Hence the name "flight recorder".
> >
> > The script can also be used in 'tail' mode to simply view KVM trace
> > events as they occur. This is handy for development and to ensure that
> > the guest is indeed running.
> >
> >
>
> Have you considered updating trace-cmd or perf-something instead? While
> each of these tools are useful we miss out on combining capabilities.
> For example you could 'perf probe' a dynamic tracepoint and flightrecord
> it together with kvm tracepoints.
This script is ideal in situations where you want to ask someone who is
not a developer to collect information. They sometimes don't want to
install software but running a small Python script is okay. So that's
the background of this tool.
That said, I agree that integrating flightrecorder mode into perf would
be very nice. I'm not sure I'll be able to come up with patches soon
but if someone is interested in doing this that would be fantastic.
Stefan
next prev parent reply other threads:[~2012-03-12 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 14:13 [Qemu-devel] [PATCH] kvm: add flightrecorder script Stefan Hajnoczi
2012-03-09 19:53 ` Anthony Liguori
2012-03-12 12:08 ` Avi Kivity
2012-03-12 14:48 ` Stefan Hajnoczi [this message]
2012-03-12 17:31 ` Avi Kivity
2012-03-13 23:46 ` Marcelo Tosatti
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=20120312144831.GA32737@stefanha-thinkpad.localdomain \
--to=stefanha@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).