From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57536) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VjPYM-000553-Jt for qemu-devel@nongnu.org; Thu, 21 Nov 2013 03:24:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VjPYG-0006JU-Kh for qemu-devel@nongnu.org; Thu, 21 Nov 2013 03:23:58 -0500 Received: from mx1.redhat.com ([209.132.183.28]:34325) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VjPYG-0006IW-Cj for qemu-devel@nongnu.org; Thu, 21 Nov 2013 03:23:52 -0500 Date: Thu, 21 Nov 2013 10:26:36 +0200 From: "Michael S. Tsirkin" Message-ID: <20131121082636.GA20073@redhat.com> References: <1385001528-12003-1-git-send-email-imammedo@redhat.com> <1385001528-12003-17-git-send-email-imammedo@redhat.com> <20131121071418.GB19703@redhat.com> <20131121081222.GG24886@G08FNSTD100614.fnst.cn.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131121081222.GG24886@G08FNSTD100614.fnst.cn.fujitsu.com> Subject: Re: [Qemu-devel] [PATCH 16/27] acpi: ich9: allow guest to clear SCI rised by GPE List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Hu Tao Cc: peter.maydell@linaro.org, mdroth@linux.vnet.ibm.com, stefanb@linux.vnet.ibm.com, mjt@tls.msk.ru, marcel.a@redhat.com, stefanha@redhat.com, armbru@redhat.com, qemu-devel@nongnu.org, vasilis.liaskovitis@profitbricks.com, quintela@redhat.com, chegu_vinod@hp.com, kraxel@redhat.com, aliguori@amazon.com, pbonzini@redhat.com, Igor Mammedov , lcapitulino@redhat.com, afaerber@suse.de On Thu, Nov 21, 2013 at 04:12:22PM +0800, Hu Tao wrote: > On Thu, Nov 21, 2013 at 09:14:18AM +0200, Michael S. Tsirkin wrote: > > On Thu, Nov 21, 2013 at 03:38:37AM +0100, Igor Mammedov wrote: > > > it fixes IRQ storm since guest isn't able to lower SCI IRQ > > > after it has been handled when it clears GPE event. > > > > > > Signed-off-by: Igor Mammedov > > > > The storm is only on memory hotplug right? > > IIRC, it happens on cpu hotplug, too. So this is a bugfix then? We should include this in 1.7?