All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: "qemu-devel" <qemu-devel@nongnu.org>, "kvm" <kvm@vger.kernel.org>
Subject: [question] e1000 interrupt storm happened because of its corresponding ioapic->irr bit always set
Date: Sat, 23 Aug 2014 18:36:40 +0800	[thread overview]
Message-ID: <201408231836387399956@sangfor.com> (raw)

Hi, all

I use a qemu-1.4.1/qemu-2.0.0 to run win7 guest, and encounter e1000 NIC interrupt storm, 
because "if (!ent->fields.mask && (ioapic->irr & (1 << i)))" is always true in __kvm_ioapic_update_eoi().

Any ideas?

Thanks,
Zhang Haoyu

WARNING: multiple messages have this Message-ID (diff)
From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: [Qemu-devel] [question] e1000 interrupt storm happened because of its corresponding ioapic->irr bit always set
Date: Sat, 23 Aug 2014 18:36:40 +0800	[thread overview]
Message-ID: <201408231836387399956@sangfor.com> (raw)

Hi, all

I use a qemu-1.4.1/qemu-2.0.0 to run win7 guest, and encounter e1000 NIC interrupt storm, 
because "if (!ent->fields.mask && (ioapic->irr & (1 << i)))" is always true in __kvm_ioapic_update_eoi().

Any ideas?

Thanks,
Zhang Haoyu

             reply	other threads:[~2014-08-23 10:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-23 10:36 Zhang Haoyu [this message]
2014-08-23 10:36 ` [Qemu-devel] [question] e1000 interrupt storm happened because of its corresponding ioapic->irr bit always set Zhang Haoyu
2014-08-25  3:07 ` Jason Wang
2014-08-25  7:17   ` [question] e1000 interrupt storm happened becauseof " Zhang Haoyu
2014-08-25  7:17     ` [Qemu-devel] " Zhang Haoyu
2014-08-25  7:29     ` Jason Wang
2014-08-25  7:29       ` [Qemu-devel] " Jason Wang
2014-08-25  8:27       ` [question] e1000 interrupt storm happened becauseof its correspondingioapic->irr " Zhang Haoyu
2014-08-25  8:27         ` [Qemu-devel] " Zhang Haoyu
2014-08-26  9:28       ` Zhang Haoyu
2014-08-26  9:28         ` [Qemu-devel] " Zhang Haoyu
2014-08-27  5:09         ` Jason Wang
2014-08-27  5:09           ` [Qemu-devel] " Jason Wang
2014-08-27  9:31           ` [Qemu-devel] [question] e1000 interrupt storm happened becauseofits " Zhang Haoyu
2014-08-28  7:12             ` Jason Wang
2014-08-28 12:55             ` [Qemu-devel] [question] e1000 interrupt storm happenedbecauseofits " Zhang Haoyu
2014-08-29  2:50               ` Jason Wang
2014-08-29  3:14               ` [Qemu-devel] [question] e1000 interrupt storm happenedbecauseofitscorrespondingioapic->irr " Zhang Haoyu
2014-08-29  4:07                 ` Zhang, Yang Z
2014-08-29  4:07                   ` [Qemu-devel] " Zhang, Yang Z
2014-08-29  4:28                   ` Jason Wang
2014-09-02 15:44               ` [Qemu-devel] [question] e1000 interrupt storm happenedbecauseofits correspondingioapic->irr " Michael S. Tsirkin
2014-09-04  1:56                 ` [Qemu-devel] [question] e1000 interrupt stormhappenedbecauseofits " Zhang Haoyu
2014-09-04  4:57                   ` Jason Wang
2014-08-25  7:32     ` [question] e1000 interrupt storm happened becauseof its corresponding ioapic->irr " Jason Wang
2014-08-25  7:32       ` [Qemu-devel] " Jason Wang

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=201408231836387399956@sangfor.com \
    --to=zhanghy@sangfor.com \
    --cc=kvm@vger.kernel.org \
    --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.