From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43547) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr9zg-0005N7-Gx for qemu-devel@nongnu.org; Wed, 19 Nov 2014 13:28:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xr9za-00024O-D3 for qemu-devel@nongnu.org; Wed, 19 Nov 2014 13:28:44 -0500 Received: from mx1.redhat.com ([209.132.183.28]:48243) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr9za-00024G-5s for qemu-devel@nongnu.org; Wed, 19 Nov 2014 13:28:38 -0500 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id sAJISaJW004190 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Wed, 19 Nov 2014 13:28:37 -0500 Message-ID: <546CE14F.7010600@redhat.com> Date: Wed, 19 Nov 2014 19:28:31 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1416254843-16859-3-git-send-email-mst@redhat.com> <546AE14E.7060606@redhat.com> <20141118074904.GA19745@redhat.com> <87y4r7o8dh.fsf@elfo.elfo> <20141119093320.GA26119@redhat.com> <87tx1v336u.fsf@blackfin.pond.sub.org> <20141119103038.GD26395@redhat.com> <874mtvo45n.fsf@elfo.elfo> <20141119133659.GA27488@redhat.com> <87r3wzmh79.fsf@elfo.elfo> <20141119154637.GC28563@redhat.com> <87d28jkuks.fsf@elfo.elfo> In-Reply-To: <87d28jkuks.fsf@elfo.elfo> Content-Type: text/plain; charset=windows-1252 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: quintela@redhat.com, "Michael S. Tsirkin" Cc: Markus Armbruster , dgilbert@redhat.com, qemu-devel@nongnu.org On 19/11/2014 17:45, Juan Quintela wrote: >> > Absolutely. And that is why callers get a callback notifying them about >> > resize. >> > >> > See? You are arriving at my design step by step :) > Then why we ever wonder about assingning the space on the 1st place? > Just got it from the migration stream? Just because then we have fewer "if (!incoming_migration())"s. Paolo