From: Gerd Hoffmann <kraxel@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/6] kvm: bios: advertise pci irqs as active high
Date: Mon, 17 Aug 2009 09:28:21 +0200 [thread overview]
Message-ID: <4A890695.5020805@redhat.com> (raw)
In-Reply-To: <20090814165018.GB16448@redhat.com>
On 08/14/09 18:50, Gleb Natapov wrote:
> On Fri, Aug 14, 2009 at 03:59:41PM +0200, Gerd Hoffmann wrote:
>> On 08/14/09 15:19, Gleb Natapov wrote:
>>> On Fri, Aug 14, 2009 at 02:21:53PM +0200, Gerd Hoffmann wrote:
>>>> From: Avi Kivity<avi@qumranet.com>
>>>>
>>>> now that kvm emulates the ioapic polarity correctly, we must describe
>>> kvm yes, but qemu doesn't. It make sense to fix qemu polarity handling
>>> in the same series.
>> Same series doesn't work. These patches are for the pcbios git tree.
>>
> We already have pcbios git tree. Cool.
Have a look at http://git.qemu.org/. Not yet live. As far I know the
plan is to (a) switch from savannah to qemu.org as master tree, (b)
import the bios trees as git submodules and (c) hook them into the qemu
build process.
>> Of course it makes sense to get more features and fixes from kvm
>> merged upstream. Feel free to join the party to speed this up ;)
>>
> kvm implements polarity in in-kernel ioapic, not in qemu one.
Ah, ok. upstream qemu probably wants to use the in-kernel ioapic too
some day, then we'll need the fixes anyway. But even without that it is
saner to have correct ACPI entries IMHO.
>> kvm, which is a good thing. Also note that the other patches which
>> fix real bugs depend on this one.
>>
> Can you elaborate which one fixes what bugs? I am not at all against
> those patches going into qemu, just curious. AFAIK current bios works
> with qemu as is.
The patch descriptions are pretty clear ...
Patch 4/6 (disallow sharing acpi irq #9) actually fixes some acpi
hickups. I've noticed the 'system_powerdown' monitor command started
working correctly recently for me, and I think this is this patch
(didn't double-check though).
cheers,
Gerd
next prev parent reply other threads:[~2009-08-17 7:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 12:21 [Qemu-devel] [PATCH 0/6] pcbios: irq routing fixes Gerd Hoffmann
2009-08-14 12:21 ` [Qemu-devel] [PATCH 1/6] kvm: bios: advertise pci irqs as active high Gerd Hoffmann
2009-08-14 13:19 ` Gleb Natapov
2009-08-14 13:59 ` Gerd Hoffmann
2009-08-14 16:50 ` Gleb Natapov
2009-08-17 7:28 ` Gerd Hoffmann [this message]
2009-08-14 12:21 ` [Qemu-devel] [PATCH 2/6] kvm: bios: restrict pci interrupts to irq 5/9/10/11 Gerd Hoffmann
2009-08-14 12:21 ` [Qemu-devel] [PATCH 3/6] kvm: bios: use extended interrupt descriptor for pci irqs Gerd Hoffmann
2009-08-14 12:21 ` [Qemu-devel] [PATCH 4/6] kvm: bios: remove irq 9 from the pci interrupt link resources Gerd Hoffmann
2009-08-14 12:21 ` [Qemu-devel] [PATCH 5/6] kvm: bios: correct default pci irq links Gerd Hoffmann
2009-08-14 12:21 ` [Qemu-devel] [PATCH 6/6] add interrupt override entries for IRQs 5, 9, 10, 11 to the MADT Gerd Hoffmann
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=4A890695.5020805@redhat.com \
--to=kraxel@redhat.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.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).