From: Stefan Weil <weil@mail.berlios.de>
To: qemu-devel@nongnu.org, Avi Kivity <avi@qumranet.com>
Subject: Re: [Qemu-devel] Breakage with local APIC routing
Date: Sun, 17 Aug 2008 19:32:28 +0200 [thread overview]
Message-ID: <48A860AC.1010307@mail.berlios.de> (raw)
In-Reply-To: <alpine.DEB.1.00.0808111616530.24820@pacific.mpi-cbg.de.mpi-cbg.de>
Johannes Schindelin schrieb:
> Hi,
>
> due to the change in revision 3371 (well, at that time, CVS was used,
> which was no better than Subversion) installation of win64 is broken in
> QEmu. The commit message reads like this:
>
> Don't route PIC interrupts through the local APIC if the local
> APIC config says so. By Ari Kivity.
>
> A bit of research showed that the patch was actually originally from Qing
> He, but he told me privately that the part that actually broke win64 (the
> removal of the call to cpu_reset_interrupt(), as opposed to moving that
> call into the "else" condition) was not part of his patch.
>
> Unfortunately, a lot has been done to the APIC handling in the meantime,
> so it is not a simple matter of a revert.
>
> Being a complete idiot when it comes to APICs, I have no clue how to fix
> the issue.
>
> However, I am quite willing to test whatever patch is thrown at me.
>
> Can somebody help?
>
> Thanks,
> Dscho
See also http://article.gmane.org/gmane.comp.emulators.qemu/24739.
EFI BIOS is affected by the same problem.
Regards,
Stefan
next prev parent reply other threads:[~2008-08-17 17:32 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 14:28 [Qemu-devel] Breakage with local APIC routing Johannes Schindelin
2008-08-13 8:14 ` [Qemu-devel] " Jan Kiszka
2008-08-13 9:08 ` Jan Kiszka
2008-08-17 15:00 ` Johannes Schindelin
2008-08-17 15:28 ` Johannes Schindelin
2008-08-17 16:52 ` Jan Kiszka
2009-08-13 16:21 ` Johannes Schindelin
2009-08-25 6:56 ` Jan Kiszka
2009-08-25 8:24 ` Mohammed Gamal
2009-08-25 8:59 ` Jan Kiszka
2009-08-25 9:09 ` Mohammed Gamal
2009-08-25 9:33 ` Jan Kiszka
2009-08-25 10:16 ` Mohammed Gamal
2009-08-25 10:21 ` Mohammed Gamal
2009-08-25 10:38 ` Jan Kiszka
2009-08-26 22:10 ` Juergen Lock
2009-08-27 17:56 ` Jan Kiszka
2009-08-29 21:18 ` Juergen Lock
2009-08-31 7:47 ` Jan Kiszka
2009-08-31 21:27 ` Juergen Lock
2009-09-01 20:12 ` Juergen Lock
2009-09-07 20:59 ` FreeBSD timing issues and qemu (was: Re: [Qemu-devel] Re: Breakage with local APIC routing) Juergen Lock
2009-09-08 2:17 ` Ryan Stone
2009-09-09 20:15 ` Juergen Lock
2009-09-09 20:39 ` Ryan Stone
2009-09-09 20:46 ` Luigi Rizzo
2009-09-10 17:46 ` Juergen Lock
2009-09-10 19:08 ` Luigi Rizzo
2009-09-10 20:44 ` Juergen Lock
2009-09-11 15:22 ` John Baldwin
2009-09-11 17:03 ` Luigi Rizzo
2009-09-11 17:01 ` John Baldwin
2009-09-12 15:48 ` Luigi Rizzo
2009-08-25 11:48 ` [Qemu-devel] Re: Breakage with local APIC routing Johannes Schindelin
2009-08-25 12:31 ` Jan Kiszka
2009-08-25 13:36 ` Johannes Schindelin
2009-08-26 7:31 ` Jan Kiszka
2009-08-26 9:27 ` Avi Kivity
2009-08-27 18:07 ` Jan Kiszka
2008-08-17 17:32 ` Stefan Weil [this message]
2008-08-17 18:58 ` Jan Kiszka
2008-08-17 20:40 ` Stefan Weil
2008-08-17 20:23 ` [Qemu-devel] " Aurelien Jarno
2008-08-17 21:10 ` Stefan Weil
2008-08-18 14:27 ` Anthony Liguori
2008-08-17 21:14 ` [Qemu-devel] " Jan Kiszka
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=48A860AC.1010307@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=avi@qumranet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).