From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LveXQ-0003O9-3F for qemu-devel@nongnu.org; Sun, 19 Apr 2009 17:26:56 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LveXL-0003MU-KD for qemu-devel@nongnu.org; Sun, 19 Apr 2009 17:26:55 -0400 Received: from [199.232.76.173] (port=56725 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LveXL-0003MR-Ei for qemu-devel@nongnu.org; Sun, 19 Apr 2009 17:26:51 -0400 Received: from mail.gmx.net ([213.165.64.20]:41749) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1LveXK-0007gZ-U0 for qemu-devel@nongnu.org; Sun, 19 Apr 2009 17:26:51 -0400 Message-ID: From: "Sebastian Herbszt" References: <49E3D91E.40208@us.ibm.com> <01bd01c9bcd3$3aaedef0$b00c9cd0$@com> <49E49BAD.70309@us.ibm.com> <01c201c9bd11$2a48d640$7eda82c0$@com> <49E4B77E.8000601@us.ibm.com> In-Reply-To: <49E4B77E.8000601@us.ibm.com> Subject: Re: [Qemu-devel] [PATCH] Fix non-ACPI Timer Interrupt Routing Date: Sun, 19 Apr 2009 23:23:20 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Beth Kon , qemu-devel@nongnu.org Cc: bochs-developers@lists.sourceforge.net, eswierk@aristanetworks.com Beth Kon wrote: > This is part of a bigger change for QEMU, incorporating irq0->inti2 > override for ACPI, and non-ACPI, driven by addition of the HPET. It > required BIOS changes as well as QEMU changes to route irq0 to inti2 of > the IOAPIC. This patch alone is not complete. I have tested the complete > solution in QEMU, thus the guards. I just tested qemu r7185 with bochs bios (without your patch) and used a Linux 2.6.27.7 guest (openSUSE-11.1-NET-i586.iso). If i don't misunderstand you this change is only needed with HPET. I have tested the following configurations which all fail: hpet enabled, no guest kernel parameters hpet enabled, guest kernel with acpi=off hpet disabled, no guest kernel parameters hpet disabled, guest kernel with acpi=off Since it even fails with HPET disabled, this change can't only be needed for HPET, can it? Ed: Have you tried your Linux guest with HPET enabled or disabled in your original report / patch? - Sebastian