From: Paolo Bonzini <pbonzini@redhat.com>
To: Chris Friesen <chris.friesen@windriver.com>,
libvir-list@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] high outage times for qemu virtio network links during live migration, trying to debug
Date: Tue, 26 Jan 2016 19:07:17 +0100 [thread overview]
Message-ID: <56A7B5D5.70003@redhat.com> (raw)
In-Reply-To: <56A7B1AE.2010902@windriver.com>
On 26/01/2016 18:49, Chris Friesen wrote:
>>
>> That doesn't exclude a bug somewhere in net/ code. It doesn't pinpoint
>> it to QEMU or vhost-net.
>>
>> In any case, what I would do is to use tracing at all levels (guest
>> kernel, QEMU, host kernel) for packet rx and tx, and find out at which
>> layer the hiccup appears.
>
> Is there a straightforward way to trace packet processing in qemu
> (preferably with millisecond-accurate timestamps)?
You can use tracing (docs/tracing.txt). There are two possibilities:
1) use existing low-level virtio tracepoints: virtqueue_fill (end of tx
and rx operation) and virtqueue_pop (beginning of tx operation).
2) add tracepoints to hw/net/virtio-net.c (virtio_net_flush_tx,
virtio_net_tx_complete, virtio_net_receive) or net/tap.c (tap_receive,
tap_receive_iov, tap_send).
Paolo
prev parent reply other threads:[~2016-01-26 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 16:41 [Qemu-devel] high outage times for qemu virtio network links during live migration, trying to debug Chris Friesen
2016-01-26 16:45 ` Daniel P. Berrange
2016-01-26 20:31 ` Chris Friesen
2016-01-26 16:50 ` Paolo Bonzini
2016-01-26 17:21 ` Chris Friesen
2016-01-26 17:31 ` Paolo Bonzini
2016-01-26 17:49 ` Chris Friesen
2016-01-26 18:07 ` Paolo Bonzini [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=56A7B5D5.70003@redhat.com \
--to=pbonzini@redhat.com \
--cc=chris.friesen@windriver.com \
--cc=libvir-list@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.