From: Anthony Liguori <aliguori@us.ibm.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH] kvm: add flightrecorder script
Date: Fri, 09 Mar 2012 13:53:22 -0600 [thread overview]
Message-ID: <4F5A5FB2.9080701@us.ibm.com> (raw)
In-Reply-To: <1331302420-29737-1-git-send-email-stefanha@linux.vnet.ibm.com>
On 03/09/2012 08:13 AM, 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.
>
> Signed-off-by: Stefan Hajnoczi<stefanha@linux.vnet.ibm.com>
> ---
> scripts/kvm/kvm_flightrecorder | 126 ++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 126 insertions(+), 0 deletions(-)
> create mode 100755 scripts/kvm/kvm_flightrecorder
I assume this should go through uq/master...
Thanks for sending this out.
Regards,
Anthony Liguori
>
> diff --git a/scripts/kvm/kvm_flightrecorder b/scripts/kvm/kvm_flightrecorder
> new file mode 100755
> index 0000000..7fb1c2d
> --- /dev/null
> +++ b/scripts/kvm/kvm_flightrecorder
> @@ -0,0 +1,126 @@
> +#!/usr/bin/env python
> +#
> +# KVM Flight Recorder - ring buffer tracing script
> +#
> +# Copyright (C) 2012 IBM Corp
> +#
> +# Author: Stefan Hajnoczi<stefanha@linux.vnet.ibm.com>
> +#
> +# This script provides a command-line interface to kvm ftrace and is designed
> +# to be used as a flight recorder that is always running. To start in-memory
> +# recording:
> +#
> +# sudo kvm_flightrecorder start 8192 # 8 MB per-cpu ring buffers
> +#
> +# The per-cpu ring buffer size can be given in KB as an optional argument to
> +# the 'start' subcommand.
> +#
> +# To stop the flight recorder:
> +#
> +# sudo kvm_flightrecorder stop
> +#
> +# To dump the contents of the flight recorder (this can be done when the
> +# recorder is stopped or while it is running):
> +#
> +# sudo kvm_flightrecorder dump>/path/to/dump.txt
> +#
> +# To observe the trace while it is running, use the 'tail' subcommand:
> +#
> +# sudo kvm_flightrecorder tail
> +#
> +# Note that the flight recorder may impact overall system performance by
> +# consuming CPU cycles. No disk I/O is performed since the ring buffer holds a
> +# fixed-size in-memory trace.
> +
> +import sys
> +import os
> +
> +tracing_dir = '/sys/kernel/debug/tracing'
> +
> +def trace_path(*args):
> + return os.path.join(tracing_dir, *args)
> +
> +def write_file(path, data):
> + open(path, 'wb').write(data)
> +
> +def enable_event(subsystem, event, enable):
> + write_file(trace_path('events', subsystem, event, 'enable'), '1' if enable else '0')
> +
> +def enable_subsystem(subsystem, enable):
> + write_file(trace_path('events', subsystem, 'enable'), '1' if enable else '0')
> +
> +def start_tracing():
> + enable_subsystem('kvm', True)
> + write_file(trace_path('tracing_on'), '1')
> +
> +def stop_tracing():
> + write_file(trace_path('tracing_on'), '0')
> + enable_subsystem('kvm', False)
> + write_file(trace_path('events', 'enable'), '0')
> + write_file(trace_path('current_tracer'), 'nop')
> +
> +def dump_trace():
> + tracefile = open(trace_path('trace'), 'r')
> + try:
> + lines = True
> + while lines:
> + lines = tracefile.readlines(64 * 1024)
> + sys.stdout.writelines(lines)
> + except KeyboardInterrupt:
> + pass
> +
> +def tail_trace():
> + try:
> + for line in open(trace_path('trace_pipe'), 'r'):
> + sys.stdout.write(line)
> + except KeyboardInterrupt:
> + pass
> +
> +def usage():
> + print 'Usage: %s start [buffer_size_kb] | stop | dump | tail' % sys.argv[0]
> + print 'Control the KVM flight recorder tracing.'
> + sys.exit(0)
> +
> +def main():
> + if len(sys.argv)< 2:
> + usage()
> +
> + cmd = sys.argv[1]
> + if cmd == '--version':
> + print 'kvm_flightrecorder version 1.0'
> + sys.exit(0)
> +
> + if not os.path.isdir(tracing_dir):
> + print 'Unable to tracing debugfs directory, try:'
> + print 'mount -t debugfs none /sys/kernel/debug'
> + sys.exit(1)
> + if not os.access(tracing_dir, os.W_OK):
> + print 'Unable to write to tracing debugfs directory, please run as root'
> + sys.exit(1)
> +
> + if cmd == 'start':
> + stop_tracing() # clean up first
> +
> + if len(sys.argv) == 3:
> + try:
> + buffer_size_kb = int(sys.argv[2])
> + except ValueError:
> + print 'Invalid per-cpu trace buffer size in KB'
> + sys.exit(1)
> + write_file(trace_path('buffer_size_kb'), str(buffer_size_kb))
> + print 'Per-CPU ring buffer size set to %d KB' % buffer_size_kb
> +
> + start_tracing()
> + print 'KVM flight recorder enabled'
> + elif cmd == 'stop':
> + stop_tracing()
> + print 'KVM flight recorder disabled'
> + elif cmd == 'dump':
> + dump_trace()
> + elif cmd == 'tail':
> + tail_trace()
> + else:
> + usage()
> +
> +if __name__ == '__main__':
> + sys.exit(main())
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <aliguori@us.ibm.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] kvm: add flightrecorder script
Date: Fri, 09 Mar 2012 13:53:22 -0600 [thread overview]
Message-ID: <4F5A5FB2.9080701@us.ibm.com> (raw)
In-Reply-To: <1331302420-29737-1-git-send-email-stefanha@linux.vnet.ibm.com>
On 03/09/2012 08:13 AM, 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.
>
> Signed-off-by: Stefan Hajnoczi<stefanha@linux.vnet.ibm.com>
> ---
> scripts/kvm/kvm_flightrecorder | 126 ++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 126 insertions(+), 0 deletions(-)
> create mode 100755 scripts/kvm/kvm_flightrecorder
I assume this should go through uq/master...
Thanks for sending this out.
Regards,
Anthony Liguori
>
> diff --git a/scripts/kvm/kvm_flightrecorder b/scripts/kvm/kvm_flightrecorder
> new file mode 100755
> index 0000000..7fb1c2d
> --- /dev/null
> +++ b/scripts/kvm/kvm_flightrecorder
> @@ -0,0 +1,126 @@
> +#!/usr/bin/env python
> +#
> +# KVM Flight Recorder - ring buffer tracing script
> +#
> +# Copyright (C) 2012 IBM Corp
> +#
> +# Author: Stefan Hajnoczi<stefanha@linux.vnet.ibm.com>
> +#
> +# This script provides a command-line interface to kvm ftrace and is designed
> +# to be used as a flight recorder that is always running. To start in-memory
> +# recording:
> +#
> +# sudo kvm_flightrecorder start 8192 # 8 MB per-cpu ring buffers
> +#
> +# The per-cpu ring buffer size can be given in KB as an optional argument to
> +# the 'start' subcommand.
> +#
> +# To stop the flight recorder:
> +#
> +# sudo kvm_flightrecorder stop
> +#
> +# To dump the contents of the flight recorder (this can be done when the
> +# recorder is stopped or while it is running):
> +#
> +# sudo kvm_flightrecorder dump>/path/to/dump.txt
> +#
> +# To observe the trace while it is running, use the 'tail' subcommand:
> +#
> +# sudo kvm_flightrecorder tail
> +#
> +# Note that the flight recorder may impact overall system performance by
> +# consuming CPU cycles. No disk I/O is performed since the ring buffer holds a
> +# fixed-size in-memory trace.
> +
> +import sys
> +import os
> +
> +tracing_dir = '/sys/kernel/debug/tracing'
> +
> +def trace_path(*args):
> + return os.path.join(tracing_dir, *args)
> +
> +def write_file(path, data):
> + open(path, 'wb').write(data)
> +
> +def enable_event(subsystem, event, enable):
> + write_file(trace_path('events', subsystem, event, 'enable'), '1' if enable else '0')
> +
> +def enable_subsystem(subsystem, enable):
> + write_file(trace_path('events', subsystem, 'enable'), '1' if enable else '0')
> +
> +def start_tracing():
> + enable_subsystem('kvm', True)
> + write_file(trace_path('tracing_on'), '1')
> +
> +def stop_tracing():
> + write_file(trace_path('tracing_on'), '0')
> + enable_subsystem('kvm', False)
> + write_file(trace_path('events', 'enable'), '0')
> + write_file(trace_path('current_tracer'), 'nop')
> +
> +def dump_trace():
> + tracefile = open(trace_path('trace'), 'r')
> + try:
> + lines = True
> + while lines:
> + lines = tracefile.readlines(64 * 1024)
> + sys.stdout.writelines(lines)
> + except KeyboardInterrupt:
> + pass
> +
> +def tail_trace():
> + try:
> + for line in open(trace_path('trace_pipe'), 'r'):
> + sys.stdout.write(line)
> + except KeyboardInterrupt:
> + pass
> +
> +def usage():
> + print 'Usage: %s start [buffer_size_kb] | stop | dump | tail' % sys.argv[0]
> + print 'Control the KVM flight recorder tracing.'
> + sys.exit(0)
> +
> +def main():
> + if len(sys.argv)< 2:
> + usage()
> +
> + cmd = sys.argv[1]
> + if cmd == '--version':
> + print 'kvm_flightrecorder version 1.0'
> + sys.exit(0)
> +
> + if not os.path.isdir(tracing_dir):
> + print 'Unable to tracing debugfs directory, try:'
> + print 'mount -t debugfs none /sys/kernel/debug'
> + sys.exit(1)
> + if not os.access(tracing_dir, os.W_OK):
> + print 'Unable to write to tracing debugfs directory, please run as root'
> + sys.exit(1)
> +
> + if cmd == 'start':
> + stop_tracing() # clean up first
> +
> + if len(sys.argv) == 3:
> + try:
> + buffer_size_kb = int(sys.argv[2])
> + except ValueError:
> + print 'Invalid per-cpu trace buffer size in KB'
> + sys.exit(1)
> + write_file(trace_path('buffer_size_kb'), str(buffer_size_kb))
> + print 'Per-CPU ring buffer size set to %d KB' % buffer_size_kb
> +
> + start_tracing()
> + print 'KVM flight recorder enabled'
> + elif cmd == 'stop':
> + stop_tracing()
> + print 'KVM flight recorder disabled'
> + elif cmd == 'dump':
> + dump_trace()
> + elif cmd == 'tail':
> + tail_trace()
> + else:
> + usage()
> +
> +if __name__ == '__main__':
> + sys.exit(main())
next prev parent reply other threads:[~2012-03-09 19:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 14:13 [PATCH] kvm: add flightrecorder script Stefan Hajnoczi
2012-03-09 14:13 ` [Qemu-devel] " Stefan Hajnoczi
2012-03-09 19:53 ` Anthony Liguori [this message]
2012-03-09 19:53 ` Anthony Liguori
2012-03-12 12:08 ` Avi Kivity
2012-03-12 12:08 ` [Qemu-devel] " Avi Kivity
2012-03-12 14:48 ` Stefan Hajnoczi
2012-03-12 14:48 ` [Qemu-devel] " Stefan Hajnoczi
2012-03-12 17:31 ` Avi Kivity
2012-03-12 17:31 ` [Qemu-devel] " Avi Kivity
2012-03-13 23:46 ` Marcelo Tosatti
2012-03-13 23:46 ` [Qemu-devel] " 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=4F5A5FB2.9080701@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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 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.