From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33039) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr6Hn-000510-VJ for qemu-devel@nongnu.org; Wed, 19 Nov 2014 09:31:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xr6Hh-0000Ps-RS for qemu-devel@nongnu.org; Wed, 19 Nov 2014 09:31:11 -0500 Received: from mx1.redhat.com ([209.132.183.28]:42825) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr6Hh-0000PR-KR for qemu-devel@nongnu.org; Wed, 19 Nov 2014 09:31:05 -0500 Message-ID: <546CA9A3.9050001@redhat.com> Date: Wed, 19 Nov 2014 15:30:59 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1416254843-16859-1-git-send-email-mst@redhat.com> <1416254843-16859-3-git-send-email-mst@redhat.com> <87a93nmggx.fsf@elfo.elfo> <546CA6F4.9050102@redhat.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 2/5] exec: qemu_ram_alloc_device, qemu_ram_resize List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: "Michael S. Tsirkin" , QEMU Developers , "Dr. David Alan Gilbert" , Juan Quintela On 19/11/2014 15:21, Peter Maydell wrote: > > But in any case this is really just memory that is auto-resized on > > migration. And it can work even if it is mapped in memory, as long as > > your resize callback (or some post_load code executed while migrating > > devices) does something useful to update the memory map. Let's call it > > like what it is. > ...so why all the "this isn't going to work in KVM" warnings > in the patchset? Just a limitation of the patches, and one thing I was going to ask to change for v2. :) Paolo