| commit | 0f254b1ae04b36e2ab2d91528297ed60d40c8c08 | |
| author | Peter Xu <peterx@redhat.com> | |
| Mon, 9 Jan 2017 08:55:53 +0000 (9 16:55 +0800) | ||
| committer | Paolo Bonzini <pbonzini@redhat.com> | |
| Mon, 16 Jan 2017 16:52:35 +0000 (16 17:52 +0100) | ||
| tree | bf635e21eb3de7554d51f6e70d589cdd30a21008 | treesnapshot (tar.gz zip) |
| parent | 8b77709c619c426635f60458b6a2e49c2dffd8ff | commitdiff |
x86: ioapic: fix fail migration when irqchip=split
Split irqchip works based on the fact that we kept the first 24 gsi
routing entries inside KVM for userspace ioapic's use. When system
boot, we'll reserve these MSI routing entries before hand. However,
after migration, we forgot to re-configure it up in the destination
side. The result is, we'll get invalid gsi routing entries after
migration (all empty), and we get interrupts with vector=0, then
strange things happen, like keyboard hang.
The solution is simple - we update them after migration, which is a
one line fix.
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <1483952153-7221-4-git-send-email-peterx@redhat.com>
Cc: qemu-stable@nongnu.org
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Split irqchip works based on the fact that we kept the first 24 gsi
routing entries inside KVM for userspace ioapic's use. When system
boot, we'll reserve these MSI routing entries before hand. However,
after migration, we forgot to re-configure it up in the destination
side. The result is, we'll get invalid gsi routing entries after
migration (all empty), and we get interrupts with vector=0, then
strange things happen, like keyboard hang.
The solution is simple - we update them after migration, which is a
one line fix.
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <1483952153-7221-4-git-send-email-peterx@redhat.com>
Cc: qemu-stable@nongnu.org
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
| hw/intc/ioapic.c | diffblobblamehistory |