From: "Stanislav" <stlintel@gmail.com>
To: qemu-devel@nongnu.org
Cc: bochs-developers@lists.sourceforge.net,
eswierk@aristanetworks.com, herbszt@gmx.de
Subject: RE: [Qemu-devel] [PATCH] Fix non-ACPI Timer Interrupt Routing
Date: Tue, 14 Apr 2009 17:56:13 +0300 [thread overview]
Message-ID: <01c201c9bd11$2a48d640$7eda82c0$@com> (raw)
In-Reply-To: <49E49BAD.70309@us.ibm.com>
>The irq0->inti2 override is not absolutely required. Running Windows
>2008 in QEMU with the emulated HPET does require it, so this is a
>QEMU-only change.
Non-absolutely required is not good answer :)
Is anything will be broken if the change is merged for Bochs as well ?
I think it will not.
And as bonus, Windows 7 32-bit is not booting under Bochs without this
change.
Stanislav
-----Original Message-----
From: qemu-devel-bounces+stlintel=gmail.com@nongnu.org
[mailto:qemu-devel-bounces+stlintel=gmail.com@nongnu.org] On Behalf Of Beth
Kon
Sent: Tuesday, April 14, 2009 5:20 PM
To: qemu-devel@nongnu.org
Cc: bochs-developers@lists.sourceforge.net; eswierk@aristanetworks.com;
herbszt@gmx.de
Subject: Re: [Qemu-devel] [PATCH] Fix non-ACPI Timer Interrupt Routing
Stanislav wrote:
> Hi,
>
> Could you explain why you doing these changes for QEMU only (with ifdef
> QEMU) ?
>
>
The irq0->inti2 override is not absolutely required. Running Windows
2008 in QEMU with the emulated HPET does require it, so this is a
QEMU-only change.
next prev parent reply other threads:[~2009-04-14 14:56 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 [this message]
2009-04-14 16:19 ` Beth Kon
2009-04-19 21:23 ` Sebastian Herbszt
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='01c201c9bd11$2a48d640$7eda82c0$@com' \
--to=stlintel@gmail.com \
--cc=bochs-developers@lists.sourceforge.net \
--cc=eswierk@aristanetworks.com \
--cc=herbszt@gmx.de \
--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.