From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:51164) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TB08m-0003D5-CD for qemu-devel@nongnu.org; Mon, 10 Sep 2012 05:18:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TB08c-0006cj-Gq for qemu-devel@nongnu.org; Mon, 10 Sep 2012 05:18:48 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45455) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TB08c-0006cR-8q for qemu-devel@nongnu.org; Mon, 10 Sep 2012 05:18:38 -0400 Message-ID: <504DB061.6060209@redhat.com> Date: Mon, 10 Sep 2012 12:18:25 +0300 From: Avi Kivity MIME-Version: 1.0 References: <1347240466-6152-1-git-send-email-mmogilvi_qemu@miniinfo.net> <1347240466-6152-6-git-send-email-mmogilvi_qemu@miniinfo.net> <504DAB38.4000407@redhat.com> <504DAE47.8090607@web.de> In-Reply-To: <504DAE47.8090607@web.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v5 5/6] i8259: fix so that dropping IRQ level always clears the interrupt request List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Paolo Bonzini , Matthew Ogilvie , "Maciej W. Rozycki" , qemu-devel@nongnu.org On 09/10/2012 12:09 PM, Jan Kiszka wrote: > On 2012-09-10 10:56, Avi Kivity wrote: >> On 09/10/2012 04:27 AM, Matthew Ogilvie wrote: >>> Intel's definition of "edge triggered" means: "asserted with a >>> low-to-high transition at the time an interrupt is registered and >>> then kept high until the interrupt is served via one of the >>> EOI mechanisms or goes away unhandled." >>> >>> So the only difference between edge triggered and level triggered >>> is in the leading edge, with no difference in the trailing edge. >> >> Hard to believe. So an edge while cpu interrupts are disabled is ignored? > > No, this is about the PIC, not the CPU interrupt inputs. I see, the interrupt is still sent to the processor; but IRR reflects that status of the input line, not a "pending interrupt" status. Will this survive live migration? If we clear IRR, then we must rely on the other end to remember the IRQ, but if processor interrupts are disabled there won't be an INTACK and the signal is lost. -- error compiling committee.c: too many arguments to function