From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: dmitry@daynix.com
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] e1000e migration
Date: Thu, 11 May 2017 13:36:40 +0100 [thread overview]
Message-ID: <20170511123639.GE2078@work-vm> (raw)
Hi Dmitry,
Have you seen any problems with e1000e migration under windows?
I've got a repeatable case where after migration with e1000e windows
hangs/almost hangs.
I'm seeing the e1000e generate interrupts at a very very high
rate (maybe ~1000 second ish?) after migration.
Some versions of qemu do it and some dont, but my attempts
at bisection lead me to code that should be irrelevant.
Prior to migration I see:
36461@1494504466.711929:e1000e_irq_pending_interrupts ICR PENDING: 0x100000 (ICR: 0x80100082, IMS: 0x1f00004)
36461@1494504466.711992:e1000e_irq_pending_interrupts ICR PENDING: 0x0 (ICR: 0x80000082, IMS: 0x1a00004)
36461@1494504466.712076:e1000e_irq_pending_interrupts ICR PENDING: 0x0 (ICR: 0x80000082, IMS: 0x1f00004)
36461@1494504466.712245:e1000e_irq_pending_interrupts ICR PENDING: 0x0 (ICR: 0x80000082, IMS: 0x1a00004)
36461@1494504466.712332:e1000e_irq_pending_interrupts ICR PENDING: 0x0 (ICR: 0x80000082, IMS: 0x1f00004)
which I think the ICR means:
31 - int asserted
20 - RxQ0 - receive queue 0 interrupt
7 - RXT0 - receiver timer interrupt
1 - TXQE - Transmit Queue empty
after migration it varies more, I'm seeing mostly:
21977@1494504516.320707:e1000e_irq_pending_interrupts ICR PENDING: 0x1000000 (ICR: 0x815000c2, IMS: 0x1a00004)
31 - int asserted
24 - 'Other'
22 - TxQ0 interrupt
20 - RxQ0 interrupt
07 - RXT0 Receiver timer interrupt
06 - RX0 - Receiver overrun
01 - TXQE - Transmit queue empty
For reference this is https://bugzilla.redhat.com/show_bug.cgi?id=1447935
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next reply other threads:[~2017-05-11 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 12:36 Dr. David Alan Gilbert [this message]
2017-05-14 13:14 ` [Qemu-devel] e1000e migration Dmitry Fleytman
2017-05-15 9:22 ` Dr. David Alan Gilbert
2017-05-15 16:13 ` Dmitry Fleytman
2017-05-15 16:14 ` Dr. David Alan Gilbert
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=20170511123639.GE2078@work-vm \
--to=dgilbert@redhat.com \
--cc=dmitry@daynix.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 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).