{"shas":[["5ea3c6b00e64d6e7a2a908739c6d74bcae1e50a1","a5b45c9af271d077f30d36aa7d9b988eed9d56eb@siemens.com","qemu-kvm: Resolve PCI upstream diffs\n\nResolve all unneeded deviations from upstream code. No functional\nchanges.\n\nSigned-off-by: Jan Kiszka <jan.kiszka@siemens.com>\nAcked-by: Michael S. Tsirkin <mst@redhat.com>\nSigned-off-by: Marcelo Tosatti <mtosatti@redhat.com>","Jan Kiszka"],["a676b1deef109b57b0a28a27fe67ff45f4a4aa1e","a5b45c9af271d077f30d36aa7d9b988eed9d56eb@siemens.com","qemu-kvm: pc: Factor out apic_next_timer\n\nFactor out apic_next_timer from apic_timer_update. The former can then\nbe used to update next_timer without actually starting the qemu timer.\nKVM's in-kernel APIC model will make use of it.\n\nSigned-off-by: Jan Kiszka <jan.kiszka@siemens.com>\nSigned-off-by: Marcelo Tosatti <mtosatti@redhat.com>","Jan Kiszka"],["2ad9e9d19f5e3ef39d0b21987071fe6e98b5aa74","a5b45c9af271d077f30d36aa7d9b988eed9d56eb@siemens.com","qemu-kvm: pc: Do not start APIC timer spuriously\n\napic_timer_update not only calculates the next timer expiry that we need\nto write out the vmstate, it may also start the timer of the user space\nAPIC model. That can cause spurious signals to the corresponding vCPU\nthread when the timer expires. Fix this by using the new apic_next_timer\nthat does not start the timer.\n\nSigned-off-by: Jan Kiszka <jan.kiszka@siemens.com>\nSigned-off-by: Marcelo Tosatti <mtosatti@redhat.com>","Jan Kiszka"],["e77ca82a3528070efe1543118a5e6d1376e4619d","958bcd1f4a7a8c36dca09fe3fa9cb5f1483adf51@redhat.com","qemu-char: use qemu_set_fd_handler/2 consistently\n\nNow that qemu_set_fd_handler and qemu_set_fd_handler2 have different\nimplementations, one using qemu iohandlers and the other glib, it is not\nsafe to mix the two when inserting/deleting handlers.\n\nFixes kvm-autotest.\n\nSigned-off-by: Marcelo Tosatti <mtosatti@redhat.com>","Marcelo Tosatti"]],"ref":"refs/heads/master","size":4,"head":"e77ca82a3528070efe1543118a5e6d1376e4619d","push_id":43033216}