On 06.12.2011 22:21, Jan Kiszka wrote: [] >> For the 0.15 .. 1.0 change, the first commit which restores the (broken >> in 0.15) functionality is this one: >> >> commit 86fbf97ceb4a9c46a609dd4ae053ba4262b68fe8 >> Author: Jan Kiszka <jan.kiszka@xxxxxxxxxxx> >> Date: Fri Oct 7 09:19:45 2011 +0200 >> >> i8259: Clear ELCR on reset >> >> The ELCR is actually part of the chipset but we model it here for >> simplicity reasons. The PIIX3 clears the ELCR on reset, which was once >> broken by 4dbe19e181. Fix this by splitting up pic_init_reset from >> pic_reset and clearing the register in the latter. >> >> Signed-off-by: Jan Kiszka <jan.kiszka@xxxxxxxxxxx> >> Signed-off-by: Blue Swirl <blauwirbel@xxxxxxxxx> >> >> Which is quite expected having in mind the commit which "broke" >> it for 0.15. > > Yep, makes a lot of sense. That patch should be applied to stable then > (who's in charge?). I'm not sure it makes much sense to continue 0.15 at this stage. >> >>> Upstream qemu 1.0 does not have this issue too. >>> >>>> [1] http://thread.gmane.org/gmane.comp.emulators.kvm.devel/82871 >>> >>> I'll try to verify this series in a moment, but hopefully it will work >>> fine too :) >> >> And that turned out to be not so easy for me. Which is this >> series against? Is there may be a git tree with this series >> applied already? > > Oops. It's against qemu-kvm's uq/master queue. Find a git tree at > > git://git.kiszka.org/qemu-kvm.git queues/kvm-irqchip This tree does not boot for me at all (on regular x86-64 setup) - it stays in bios after "Booting from hard disk" with 100% CPU usage. /mjt -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
