Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lt06P-0005Hq-Ns for qemu-devel@nongnu.org; Sun, 12 Apr 2009 09:52:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lt06K-0005FM-8l for qemu-devel@nongnu.org; Sun, 12 Apr 2009 09:52:04 -0400 Received: from [199.232.76.173] (port=43086 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lt06K-0005F8-2i for qemu-devel@nongnu.org; Sun, 12 Apr 2009 09:52:00 -0400 Received: from mail.gmx.net ([213.165.64.20]:44016) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1Lt06J-00052R-EZ for qemu-devel@nongnu.org; Sun, 12 Apr 2009 09:51:59 -0400 Message-ID: <6F64D9258BE74551983017A7F9B94472@FSCPC> From: "Sebastian Herbszt" References: <1239419318.20633.10.camel@localhost.localdomain> In-Reply-To: <1239419318.20633.10.camel@localhost.localdomain> Date: Sun, 12 Apr 2009 15:51:16 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH] Fix timer interrupt routing for non-ACPI guest Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ed Swierk , bochs-developers@lists.sourceforge.net, qemu-devel@nongnu.org Ed Swierk wrote: > Qemu 0.10.2 is unable to boot a non-ACPI kernel due to a BIOS bug: > > ENABLING IO-APIC IRQs > ..TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1 > ..MP-BIOS bug: 8254 timer not connected to IO-APIC > ...trying to set up timer (IRQ0) through the 8259A ... > ..... (found apic 0 pin 0) ... > ....... failed. > ...trying to set up timer as Virtual Wire IRQ... I tried Linux 2.6.27.7 and it seems to hang after "...trying to set up timer as Virtual Wire IRQ...". On 2.6.25.5 it managed to use Virtual Wire mode: ..TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1 ..MP-BIOS bug: 8254 timer not connected to IO-APIC ...trying to set up timer (IRQ0) through the 8259A ... failed. ...trying to set up timer as Virtual Wire IRQ... works. testing the IO APIC....................... .................................... done. > The interrupt routing table in the MPTABLE needs to route the timer > interrupt (IRQ 0) to IOAPIC pin 2. Do you refer here to "5.3 Assigning of I/O Interrupts to the APIC I/O Unit" from MultiProcessor Specification 1.4 or some other documentation? > A similar bug was recently fixed in the ACPI table code. Can you point me to the patch? > This patch fixes the problem for non-ACPI guests. Linux displays the following without any patch: Int: type 0, pol 0, trig 0, bus 00, IRQ 00, APIC ID 1, APIC INT 00 Int: type 0, pol 0, trig 0, bus 00, IRQ 01, APIC ID 1, APIC INT 01 Int: type 0, pol 0, trig 0, bus 00, IRQ 02, APIC ID 1, APIC INT 02 Int: type 0, pol 0, trig 0, bus 00, IRQ 03, APIC ID 1, APIC INT 03 ... ..TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1 [older Linux output] IRQ to pin mappings: IRQ0 -> 0:0 IRQ1 -> 0:1 IRQ2 -> 0:2 IRQ3 -> 0:3 With your patch it's: Int: type 0, pol 0, trig 0, bus 00, IRQ 00, APIC ID 1, APIC INT 00 Int: type 0, pol 0, trig 0, bus 00, IRQ 01, APIC ID 1, APIC INT 01 Int: type 0, pol 0, trig 0, bus 00, IRQ 00, APIC ID 1, APIC INT 02 Int: type 0, pol 0, trig 0, bus 00, IRQ 03, APIC ID 1, APIC INT 03 ... ..TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1 [older Linux output] IRQ to pin mappings: IRQ0 -> 0:0-> 0:2 IRQ1 -> 0:1 IRQ3 -> 0:3 Is this mapping correct or should it rather be the following? ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 IRQ0 -> 0:2 IRQ1 -> 0:1 IRQ3 -> 0:3 - Sebastian