From: "=?utf-8?B?WmhhbmcgSGFveXU=?=" Subject: =?utf-8?B?UmU6IFtxdWVzdGlvbl0gZTEwMDAgaW50ZXJydXB0IHN0b3JtIGhhcHBlbmVkIGJlY2F1c2VvZiBpdHMgY29ycmVzcG9uZGluZ2lvYXBpYy0+aXJyIGJpdCBhbHdheXMgc2V0?= Date: Tue, 26 Aug 2014 17:28:26 +0800 Message-ID: <201408261728240882530@sangfor.com> References: <201408231836387399956@sangfor.com>, <53FAA874.70703@redhat.com>, <201408251517235889695@sangfor.com>, <53FAE5EB.8080809@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: "=?utf-8?B?SmFzb24gV2FuZw==?=" , "=?utf-8?B?cWVtdS1kZXZlbA==?=" , "=?utf-8?B?a3Zt?=" Return-path: Received: from smtp.sanfor.com ([58.251.49.30]:51514 "EHLO mail.sangfor.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S932261AbaHZJao (ORCPT ); Tue, 26 Aug 2014 05:30:44 -0400 Sender: kvm-owner@vger.kernel.org List-ID: >>>> 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? >>> We meet this several times: search the autoneg patches for an example of >>> workaround for this in qemu, and patch kvm: ioapic: conditionally delay >>> irq delivery during eoi broadcast for an workaround in kvm (rejected). >>> >> Thanks, Jason, >> I searched "e1000 autoneg" in gmane.comp.emulators.qemu, and found below patches, >> http://thread.gmane.org/gmane.comp.emulators.qemu/143001/focus=143007 > >This series is the first try to fix the guest hang during guest >hibernation or driver enable/disable. >> http://thread.gmane.org/gmane.comp.emulators.qemu/284105/focus=284765 >> http://thread.gmane.org/gmane.comp.emulators.qemu/186159/focus=187351 > >Those are follow-up that tries to fix the bugs introduced by the autoneg >hack. >> which one tries to fix this problem, or all of them? > >As you can see, those kinds of hacking may not as good as we expect >since we don't know exactly how e1000 works. Only the register function >description from Intel's manual may not be sufficient. And you can >search e1000 in the archives and you can find some behaviour of e1000 >registers were not fictionalized like what spec said. It was really >suggested to use virtio-net instead of e1000 in guest. >> Will the "[PATCH] kvm: ioapic: conditionally delay irq delivery during eoi broadcast" add delay to virtual interrupt injection sometimes, then some time delay sensitive applications will be impacted? Thanks, Zhang Haoyu