[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH V2 3/5] Introduce premigrate RunState.
From: |
Anthony PERARD |
Subject: |
Re: [Qemu-devel] [PATCH V2 3/5] Introduce premigrate RunState. |
Date: |
Thu, 5 Jan 2012 12:26:31 +0000 |
On Tue, Jan 3, 2012 at 19:05, Luiz Capitulino <address@hidden> wrote:
> On Mon, 19 Dec 2011 17:27:55 +0000
> Anthony PERARD <address@hidden> wrote:
>
>> On Thu, 15 Dec 2011, Luiz Capitulino wrote:
>>
>> > On Thu, 15 Dec 2011 09:14:00 -0600
>> > Anthony Liguori <address@hidden> 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?
I suppose I can use it, by setting INMIGRATE earlier. I was afraid to
change the meaning of inmigrate, but this seems fine in the QEMU point
of view.
> PS: sorry for the delay, I was on vacation.
This is fine, me too :).
--
Anthony PERARD