-
ppc-for-2.6-20160426df18b2db · ·
ppc patch queue for 2016-04-26 (last minute qemu-2.6 fix) This just has one, last-minute, fix for a serious regression of memory hotplug. Patch author's comment: Really sorry for the way last-minute fix, but without this memory hotplug is totally broken :( Hoping to get this in for Wednesday's RC4, which I think will be the final before release. -
ppc-for-2.6-20160423da34fed7 · ·
ppc patch queue for 2016-03-23 A single fix for a bug in parameter handling for the spapr PCI host bridge.
-
ppc-for-2.6-20160419ed3d807b · ·
ppc patch queueu for 2016-04-19 A single fix for a regression since 2.5. This should be the last ppc pull request for 2.6.
-
ppc-for-2.6-20160418aa378598 · ·
ppc patch queue for 2-16-04-18 Three bugfixe patches for 2.6 here. * Two for bad implementation of some of the strong load/store instructions * One for bad migration of the XER register. This is a regression from 2.5, cause by a change in the way we represent at XER during runtime.
-
ppc-for-2.6-20160408a110655a · ·
ppc patch queue for 2016-04-08 Just a single bugfix for spapr in this batch, but I want to make sure it gets in for 2.6.
-
ppc-for-2.6-20160405efdaf797 · ·
ppc patch queue for 2016-03-24 Three bugfixes for target-ppc, pseries machine type and related devices. 1. Fix a bug in the core code where kvm_vcpu_dirty would not be set before the very first system reset. This meant that if things in the reset path did their own cpu_synchronize_state() it would pull stale data out of KVM. On ppc this, in combination with a previous cleanup meant that the MSR would be zeroed before entry, instead of correctly having the SF (64-bit mode) bit set. 2. Allow immediate detach of hot-added PCI devices which haven't yet been announced to the guest. This fixes a regression: because of a case where we now defer announcement of non-zero functions to the guest, an incorrect hot-add of such a device can't be backed out until the add is completed, which is counter-intuitive to say the least. 3. Fix migration of alternate interrupt locations. The location of interrupt vectors can be affected by the LPCR, and we weren't correctly recalculating this after migration of a non-standard LPCR value.
-
vfio-update-20160328.055efcc53 · ·
VFIO updates 2016-03-28 - Use 128bit math to avoid asserts with IOMMU regions (Bandan Das)
-
ppc-for-2.6-201603249d0e5c8c · ·
ppc patch queue for 2016-03-24 Accumulated patches for target-ppc, pseries machine type and related devices. * Preliminary patches from BenH & Cédric Le Goater's powernv code * We don't want the full machine type before 2.7 * Adding some of the SPRs also fixes migration corner cases for spapr (when qemu has no knowledge of the registers, they're obviously not migrated) * We include some patches that aren't strictly fixes, but make applying the others easier, and they're low risk * Fix to buffer management which significantly improves throughput in the spapr-llan virtual network device * Start with 64-bit mode enabled on spapr. This is the way it's supposed to be but we broke it a while back and didn't notice because Linux guests cope anyway. * Picked up by kvm-unit-tests * Still some bugs here that I'm working on -
ppc-for-2.6-201603163356128c · ·
ppc patch queue for 2016-03-16 Accumulated patches for target-ppc, pseries machine type and related devices. As we are now in soft freeze, these are mostly fixes. * Fix KVM migration for several SPRs that qemu didn't handle * Clean up handling of SDR1, which allows a fix to the gdbstub * Fix a race in spapr_rng * Fix a bug with multifunction hotplug The exception is the 7 patches to allow EEH on spapr-pci-host-bridge devices (rather than the special and poorly designed spapr-vfio-pci-host-bridge device). I believe these are low risk of breaking non-EEH cases, and EEH cases were little used in practice previously (since libvirt did not support the special device amongst other things). It did have a draft posted before the soft freeze, removes a very ugly VFIO interface, and removes device we'd like to deprecate sooner rather than later. So, I'm hoping we can squeeze these in during the soft freeze. This includes two patches to the VFIO code, which Alex Williamson has indicated he's ok with coming through my tree.