From: "Michael S. Tsirkin" <mst@redhat.com>
To: Sameeh Jubran <sameeh@daynix.com>
Cc: Dmitry Fleytman <dmitry@daynix.com>,
Yan Vugenfirer <yan@daynix.com>, Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] e1000: Introducing an upper bound of interrupts
Date: Tue, 22 Mar 2016 13:23:32 +0200 [thread overview]
Message-ID: <20160322132151-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <1458200278-11940-1-git-send-email-sameeh@daynix.com>
On Thu, Mar 17, 2016 at 09:37:56AM +0200, Sameeh Jubran wrote:
> This patch series introduces an upper bound for the number of interrupts
> per second. This feature is supported by the real hardware, however up
> until now it wasn't implemented in e1000. This feature is very
> significant, it can prevent an interrupt storm by giving the driver
> a bounded inter-interrupt interval to handle interrupts.
>
> This patch was made after observing an interrupt storm in Windows 10
> when disabling e1000.
Interesting. There's actually a kvm hack to work-around
this in older guests. We always assumed this is a guest bug,
but it might be worth testing whether the below patch is
still required after fixing qemu.
commit 184564efae4d775225c8fe3b762a56956fb1f827
Author: Zhang Haoyu <zhanghy@sangfor.com>
Date: Thu Sep 11 16:47:04 2014 +0800
kvm: ioapic: conditionally delay irq delivery duringeoi broadcast
Currently, we call ioapic_service() immediately when we find the irq is still
> How reproducible:
>
> Steps to reproduce:
> 1. Start Win 10 guest with e1000 device.
> 2. Go to device manager and try to disable and enable the device.
> 3. After several enable/disable to the device the guest hangs when
> the device is being disabled.
>
> Actual results:
> Guest hang after click OK button.
>
> Expected results:
> Device is disabled.
>
> After applying the patch the guest no longer hangs, and an Iperf test
> ran successfully.
>
> Sameeh Jubran (2):
> e1000: Fixing interrupts pace.
> Revert "e1000: fix hang of win2k12 shutdown with flood ping"
>
> hw/net/e1000.c | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> --
> 2.5.0
>
prev parent reply other threads:[~2016-03-22 11:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 7:37 [Qemu-devel] [PATCH 0/2] e1000: Introducing an upper bound of interrupts Sameeh Jubran
2016-03-17 7:37 ` [Qemu-devel] [PATCH 1/2] e1000: Fixing interrupts pace Sameeh Jubran
2016-05-04 11:34 ` Shmulik Ladkani
2016-05-16 5:58 ` Sameeh Jubran
2016-05-16 10:55 ` Shmulik Ladkani
2016-05-17 18:26 ` Sameeh Jubran
2016-03-17 7:37 ` [Qemu-devel] [PATCH 2/2] Revert "e1000: fix hang of win2k12 shutdown with flood ping" Sameeh Jubran
2016-03-17 19:51 ` [Qemu-devel] [PATCH 0/2] e1000: Introducing an upper bound of interrupts Denis V. Lunev
2016-03-18 1:34 ` Jason Wang
2016-03-21 8:25 ` Sameeh Jubran
2016-03-22 11:23 ` Michael S. Tsirkin [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=20160322132151-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=dmitry@daynix.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sameeh@daynix.com \
--cc=yan@daynix.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.