From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:39231) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ri9gW-00077i-C5 for qemu-devel@nongnu.org; Tue, 03 Jan 2012 14:06:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ri9gV-00016p-8D for qemu-devel@nongnu.org; Tue, 03 Jan 2012 14:06:08 -0500 Received: from mx1.redhat.com ([209.132.183.28]:5772) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ri9gU-00016Y-T1 for qemu-devel@nongnu.org; Tue, 03 Jan 2012 14:06:07 -0500 Date: Tue, 3 Jan 2012 17:05:55 -0200 From: Luiz Capitulino Message-ID: <20120103170555.3a32ac1b@doriath> In-Reply-To: References: <1323467645-24271-1-git-send-email-anthony.perard@citrix.com> <1323467645-24271-4-git-send-email-anthony.perard@citrix.com> <4EEA0EB8.4020203@codemonkey.ws> <20111215143131.75239a3e@doriath> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH V2 3/5] Introduce premigrate RunState. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony PERARD Cc: Xen Devel , QEMU-devel , Stefano Stabellini On Mon, 19 Dec 2011 17:27:55 +0000 Anthony PERARD wrote: > On Thu, 15 Dec 2011, Luiz Capitulino wrote: > > > On Thu, 15 Dec 2011 09:14:00 -0600 > > Anthony Liguori wrote: > > > > > On 12/09/2011 03:54 PM, Anthony PERARD wrote: > > > > This new state will be used by Xen functions to know QEMU will wait for a > > > > migration. This is important to know for memory related function because the > > > > memory is already allocated and reallocated them will not works. > > > > How is premigrate different from inmigrate? It looks like the same thing to me. > > The inmigrate state is used during machine initilisation. So this state > replace the prelauch state (during machine.init) when a migration will be done. > > inmigrate is set only when the initilisation of the machine is over. Do you need both? What about setting inmigrate when initializing the machine and using it instead? PS: sorry for the delay, I was on vacation. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luiz Capitulino Subject: Re: [PATCH V2 3/5] Introduce premigrate RunState. Date: Tue, 3 Jan 2012 17:05:55 -0200 Message-ID: <20120103170555.3a32ac1b@doriath> References: <1323467645-24271-1-git-send-email-anthony.perard@citrix.com> <1323467645-24271-4-git-send-email-anthony.perard@citrix.com> <4EEA0EB8.4020203@codemonkey.ws> <20111215143131.75239a3e@doriath> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: Anthony PERARD Cc: Xen Devel , QEMU-devel , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On Mon, 19 Dec 2011 17:27:55 +0000 Anthony PERARD wrote: > On Thu, 15 Dec 2011, Luiz Capitulino wrote: > > > On Thu, 15 Dec 2011 09:14:00 -0600 > > Anthony Liguori wrote: > > > > > On 12/09/2011 03:54 PM, Anthony PERARD wrote: > > > > This new state will be used by Xen functions to know QEMU will wait for a > > > > migration. This is important to know for memory related function because the > > > > memory is already allocated and reallocated them will not works. > > > > How is premigrate different from inmigrate? It looks like the same thing to me. > > The inmigrate state is used during machine initilisation. So this state > replace the prelauch state (during machine.init) when a migration will be done. > > inmigrate is set only when the initilisation of the machine is over. Do you need both? What about setting inmigrate when initializing the machine and using it instead? PS: sorry for the delay, I was on vacation.