From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46328)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <quintela@redhat.com>) id 1Xr8O7-00017l-0S
	for qemu-devel@nongnu.org; Wed, 19 Nov 2014 11:45:57 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <quintela@redhat.com>) id 1Xr8O0-0000Ko-M2
	for qemu-devel@nongnu.org; Wed, 19 Nov 2014 11:45:50 -0500
Received: from mx1.redhat.com ([209.132.183.28]:48986)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <quintela@redhat.com>) id 1Xr8O0-0000Ki-2P
	for qemu-devel@nongnu.org; Wed, 19 Nov 2014 11:45:44 -0500
Received: from int-mx10.intmail.prod.int.phx2.redhat.com
	(int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23])
	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id sAJGjhCN030192
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256
	verify=FAIL)
	for <qemu-devel@nongnu.org>; Wed, 19 Nov 2014 11:45:43 -0500
From: Juan Quintela <quintela@redhat.com>
In-Reply-To: <20141119154637.GC28563@redhat.com> (Michael S. Tsirkin's message
	of "Wed, 19 Nov 2014 17:46:37 +0200")
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>
Date: Wed, 19 Nov 2014 17:45:39 +0100
Message-ID: <87d28jkuks.fsf@elfo.elfo>
MIME-Version: 1.0
Content-Type: text/plain
Subject: Re: [Qemu-devel] [PATCH 2/5] exec: qemu_ram_alloc_device,
	qemu_ram_resize
Reply-To: quintela@redhat.com
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, Markus Armbruster <armbru@redhat.com>, dgilbert@redhat.com, qemu-devel@nongnu.org

"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Wed, Nov 19, 2014 at 02:51:38PM +0100, Juan Quintela wrote:

> Actually yes: devices that want this functionality need to call
> the new API.
> At the point where API is called, would be the best place to
> put in an explanation why it should be resizeable.
>
>
>> In general it would not work, even if it
>> works on one particular case.  If they are bigger, it is because device
>> code use that for something.  not necesarely something that can be
>> ignored.
>> 
>> Later, Juan.
>
> 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?

Later, Juan.