From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58043) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr68X-0002XZ-14 for qemu-devel@nongnu.org; Wed, 19 Nov 2014 09:21:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xr68Q-00056Q-G1 for qemu-devel@nongnu.org; Wed, 19 Nov 2014 09:21:36 -0500 Received: from mail-lb0-f169.google.com ([209.85.217.169]:63204) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr68Q-000561-9y for qemu-devel@nongnu.org; Wed, 19 Nov 2014 09:21:30 -0500 Received: by mail-lb0-f169.google.com with SMTP id 10so565248lbg.14 for ; Wed, 19 Nov 2014 06:21:29 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <546CA6F4.9050102@redhat.com> 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> From: Peter Maydell Date: Wed, 19 Nov 2014 14:21:09 +0000 Message-ID: Content-Type: text/plain; charset=UTF-8 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: Paolo Bonzini Cc: "Michael S. Tsirkin" , QEMU Developers , "Dr. David Alan Gilbert" , Juan Quintela On 19 November 2014 14:19, Paolo Bonzini wrote: > On 19/11/2014 15:10, Peter Maydell wrote: >> Would it be feasible to just have the migration code provide >> an API for registering things to be migrated in the live >> migration stage, rather than creating memory regions which >> you can't actually use for most of the purposes the memory >> region API exists for? > > It does already, for example PPC uses it for its IOMMU tables. > > 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? thanks -- PMM