From: Laszlo Ersek <lersek@redhat.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] some virtio-scsi tracing
Date: Thu, 29 Aug 2013 15:36:54 +0200 [thread overview]
Message-ID: <521F4E76.2090507@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
Recently we had to track down a (remote) problem with virtio-scsi tape
passthrough. Paolo asked me if I could turn my ad-hoc debug printf()s
into trace events.
I tested the series in the following way:
- enabled the two "processing hungry" events in "trace-events",
- built & installed qemu,
- using libvirt, started a guest with a passthru USB flash drive,
- logged in to the guest,
- on the host, enabled all virtio_scsi_* events using "virsh
qemu-monitor-command",
- in the guest:
- mounted the disk,
- listed the directory tree,
- unmounted the disk,
- on the host, physically disconnected the flash drive.
I'm attaching the trace output (stderr backend, saved by libvirt); you
should be able to pair segments of the file with the above actions.
Laszlo Ersek (2):
qemu_hexstr(): hexdump a small buffer to a string, for in-line
printing
add some virtio-scsi trace events
include/qemu-common.h | 11 +++++++
hw/scsi/virtio-scsi.c | 76 +++++++++++++++++++++++++++++++++++++++++++++++--
util/hexdump.c | 20 +++++++++++++
trace-events | 19 ++++++++++++
4 files changed, 123 insertions(+), 3 deletions(-)
[-- Attachment #2: fw-ovmf.g-rhel7.e-upstream.log.xz --]
[-- Type: application/x-xz, Size: 4084 bytes --]
next reply other threads:[~2013-08-29 13:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 13:36 Laszlo Ersek [this message]
2013-08-29 13:37 ` [Qemu-devel] [PATCH 1/2] qemu_hexstr(): hexdump a small buffer to a string, for in-line printing Laszlo Ersek
2013-08-29 16:32 ` Markus Armbruster
2013-08-29 13:37 ` [Qemu-devel] [PATCH 2/2] add some virtio-scsi trace events Laszlo Ersek
2013-08-29 13:59 ` Paolo Bonzini
2013-08-29 14:18 ` Laszlo Ersek
2013-08-29 14:53 ` Paolo Bonzini
2013-08-29 15:35 ` Laszlo Ersek
2013-08-29 15:42 ` Paolo Bonzini
2013-09-04 14:21 ` Stefan Hajnoczi
2013-09-05 1:26 ` Laszlo Ersek
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=521F4E76.2090507@redhat.com \
--to=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--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 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.