On Wed, Jul 15, 2015 at 06:26:03PM +0300, Andrey Korolyov wrote: > On Wed, Jul 15, 2015 at 6:18 PM, Igor Mammedov <imamm...@redhat.com> wrote: > > On Thu, 9 Jul 2015 20:04:35 +0300 > > Andrey Korolyov <and...@xdel.ru> wrote: > > > >> On Wed, Jul 8, 2015 at 6:46 PM, Igor Mammedov <imamm...@redhat.com> wrote: > >> > On Wed, 8 Jul 2015 13:01:05 +0300 > >> > "Michael S. Tsirkin" <m...@redhat.com> wrote: > >> > > >> > [...] > >> >> - this fixes qemu on current kernels, so it's a bugfix > >> >> > >> >> - this changes the semantics of memory hot unplug slightly > >> >> so I think it's important to merge in 2.4 before we > >> >> release qemu with memory hot unplug, this way we > >> >> won't have to maintain old semantics forever > >> > concerning semantic change, I've just chatted with Peter > >> > who implemented libvirt side of the memory hotplug stack. > >> > And it's not a problem for libvirt since it always does > >> > unplug dimm -> remove backend sequence. > >> > > >> > > >> > >> > >> Just for the record - top of the series somehow fixed mysterious guest > >> memory corruption issue described in > >> https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg03117.html > >> which existed right from a moment of a memory hotplug introduction, I > >> checked series for its disappearance only with vhost for now. Thanks > >> Igor! > > just to be sure which patch exactly fixed issue for you? > > > > Had not bisected this yet, 2.3 is fairly distant from mine production > yet... will post a result today or tomorrow. Until then, I`ll be > absolutely out of clues of what was behind mentioned corruption.
Igor merely asked which of his 8 patches fixed it. -- MST