[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v5 17/45] Add wrappers and handlers for sending/
Re: [Qemu-devel] [PATCH v5 17/45] Add wrappers and handlers for sending/receiving the postcopy-ram migration messages.
Sat, 28 Mar 2015 17:00:00 +0100
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
On 27/03/2015 11:48, Dr. David Alan Gilbert wrote:
> > So, I like the idea of one message per action in principle - but only
> > if that action really is well-defined without reference to what
> > operations come before and after it. If there are hidden dependencies
> > about what actions have to come in what order, I'd rather bake that
> > into the command structure.
> In no way is it hidden; the commands match the state transitions.
So is there only one writer thread? In which states can the other
threads read the postcopy state, and why is sequential consistency
important? That is, in threads other than the writer, how does reading
the state interact with other reads and writes?