From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58089) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZDFFr-000066-Iy for qemu-devel@nongnu.org; Thu, 09 Jul 2015 13:05:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZDFFq-0001j9-C4 for qemu-devel@nongnu.org; Thu, 09 Jul 2015 13:04:59 -0400 Received: from mail-la0-x230.google.com ([2a00:1450:4010:c03::230]:33811) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZDFFp-0001i3-SW for qemu-devel@nongnu.org; Thu, 09 Jul 2015 13:04:58 -0400 Received: by lagx9 with SMTP id x9so250162593lag.1 for ; Thu, 09 Jul 2015 10:04:55 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20150708174602.4126f466@igors-macbook-pro.local> References: <1436348808-223033-1-git-send-email-imammedo@redhat.com> <20150708125901-mutt-send-email-mst@redhat.com> <20150708174602.4126f466@igors-macbook-pro.local> From: Andrey Korolyov Date: Thu, 9 Jul 2015 20:04:35 +0300 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [RFC v3 0/8] Fix QEMU crash during memory hotplug with vhost=on List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Igor Mammedov Cc: Paolo Bonzini , Peter Krempa , "qemu-devel@nongnu.org" , "Michael S. Tsirkin" On Wed, Jul 8, 2015 at 6:46 PM, Igor Mammedov wrote: > On Wed, 8 Jul 2015 13:01:05 +0300 > "Michael S. Tsirkin" 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!