qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 1/6] kvm: bios: advertise pci irqs as active hig


From: Gerd Hoffmann
Subject: Re: [Qemu-devel] [PATCH 1/6] kvm: bios: advertise pci irqs as active high
Date: Mon, 17 Aug 2009 09:28:21 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre Thunderbird/3.0b2

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<address@hidden>

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]