qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Beth Kon <eak@us.ibm.com>,
	qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] Re: [RFC][PATCH] disable special ioapic inti0 routing
Date: Sat, 07 Feb 2009 03:09:43 +0100	[thread overview]
Message-ID: <498CED67.20403@web.de> (raw)
In-Reply-To: <498CE430.8010708@codemonkey.ws>

[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]

Anthony Liguori wrote:
> Jan Kiszka wrote:
>> Anthony Liguori wrote:
>>  
>>> Jan Kiszka wrote:
>>>    
>>>> This patch comes from the kvm tree and fixes the timer IRQ routing for
>>>> me which is broken from the POV of certain Linux guest kernels. As I'm
>>>> not up-to-date with the development around that problematic hunk, I'm
>>>> leaving it to someone more deeply involved to sign this off. But please
>>>> commit some fix.
>>>>         
>>> Are you using an old bios by chance?  The reason this fixes KVM has
>>> nothing to do with QEMU FWIW so if this fixes something for you, it's
>>> just a coincidence.
>>>     
>>
>> My first thought as well, but the binary bios from latest svn made no
>> difference.
>>   
> 
> What linux guests broke?

An old 32-bit customized one. And it turned out that it had, for some
reasons I don't recall anymore, ACPI disabled. So it missed the timer
IRQ pin moving QEMU is doing. At the same time, some very similar kernel
with ACPI enabled boots fine. Think I should delete the former from my
test image...

Sorry for the noise,
Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

      reply	other threads:[~2009-02-07  2:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06 23:30 [Qemu-devel] [RFC][PATCH] disable special ioapic inti0 routing Jan Kiszka
2009-02-06 23:51 ` Anthony Liguori
2009-02-07  0:07   ` [Qemu-devel] " Jan Kiszka
2009-02-07  1:30     ` Anthony Liguori
2009-02-07  2:09       ` Jan Kiszka [this message]

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=498CED67.20403@web.de \
    --to=jan.kiszka@web.de \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=eak@us.ibm.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).