From: "Sebastian Herbszt" <herbszt@gmx.de>
To: Beth Kon <eak@us.ibm.com>, qemu-devel@nongnu.org
Cc: bochs-developers@lists.sourceforge.net, eswierk@aristanetworks.com
Subject: Re: [Qemu-devel] [PATCH] Fix non-ACPI Timer Interrupt Routing
Date: Sun, 19 Apr 2009 23:23:20 +0200 [thread overview]
Message-ID: <DB921E61F09F4AC796FAA452D5494B74@FSCPC> (raw)
In-Reply-To: <49E4B77E.8000601@us.ibm.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
next prev parent reply other threads:[~2009-04-19 21:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 0:30 [Qemu-devel] [PATCH] Fix non-ACPI Timer Interrupt Routing Beth Kon
2009-04-14 1:10 ` Ryan Harper
2009-04-14 13:43 ` Beth Kon
2009-04-14 7:32 ` Stanislav
2009-04-14 14:20 ` Beth Kon
2009-04-14 14:56 ` Stanislav
2009-04-14 16:19 ` Beth Kon
2009-04-19 21:23 ` Sebastian Herbszt [this message]
2009-04-20 18:06 ` Beth Kon
2009-04-21 22:22 ` [Qemu-devel] " Sebastian Herbszt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DB921E61F09F4AC796FAA452D5494B74@FSCPC \
--to=herbszt@gmx.de \
--cc=bochs-developers@lists.sourceforge.net \
--cc=eak@us.ibm.com \
--cc=eswierk@aristanetworks.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.