From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41208)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <m.gibula@beyond.pl>) id 1X84mj-0002C3-6C
	for qemu-devel@nongnu.org; Fri, 18 Jul 2014 05:49:09 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <m.gibula@beyond.pl>) id 1X84mZ-0001PE-Fq
	for qemu-devel@nongnu.org; Fri, 18 Jul 2014 05:49:01 -0400
Received: from mx.beyond.pl ([92.43.117.49]:50108)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <m.gibula@beyond.pl>) id 1X84mZ-0001P1-8q
	for qemu-devel@nongnu.org; Fri, 18 Jul 2014 05:48:51 -0400
Message-ID: <53C8ED79.2040908@beyond.pl>
Date: Fri, 18 Jul 2014 11:48:41 +0200
From: =?UTF-8?B?TWFyY2luIEdpYnXFgmE=?= <m.gibula@beyond.pl>
MIME-Version: 1.0
References: <CABYiri8_naTkFgVJEwy9O52gRYHTVGwo-6sH-r+0FOFPf0Zm8w@mail.gmail.com>	<CABYiri_Jb+cAty591-cmqsgxbZne-9BZeDwDOFdAm1gaKtpgzQ@mail.gmail.com>	<20140715210948.GA20036@amt.cnet>	<CABYiri9Z3iDPn1JRSR-_x4SntBZms3yQPaChSbyRFAi2W9yScw@mail.gmail.com>	<53C5A4C9.80609@redhat.com>	<CABYiri9MigkURgV273kVjhnYxLz_WnQtsZzToy531vY0cjiGkQ@mail.gmail.com>	<20140716011634.GA30717@amt.cnet>	<CABYiri96UbyO238wYKz9OC5Tn69jZ7XdaoEX1A2ucbPTrbA1tg@mail.gmail.com>	<20140716115229.GA7741@amt.cnet>	<CABYiri9mNpaY35EVGLTjR6c7SkY2HgttpN_3NihFy2jcOQ9raQ@mail.gmail.com>	<CABYiri_vDLR=PATk1Lb99nDcJf4Q-yajayyMR1Tuv6bfwVUjgQ@mail.gmail.com>	<53C6EE7C.60702@beyond.pl>	<CABYiri8HdQhsoaf2=FHLG+KyrNj05FT015bNcEk9ngH
	6Dxo7dQ@mail.gmail.com>	<53C79C41.4000800@beyond.pl>	<53C7B989.9000203@beyond.pl>	<CABYiri-aeP=0NcKaoaa=_au9sruvxnPVNri_Vy2KxKFHRj2fUw@mail.gmail.com>
	<53C7CEE5.4080006@beyond.pl> <53C8DF68.5040705@redhat.com>
	<53C8E9BD.4070406@beyond.pl> <53C8EAF7.7050909@redhat.com>
In-Reply-To: <53C8EAF7.7050909@redhat.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] latest rc: virtio-blk hangs forever after migration
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: Paolo Bonzini <pbonzini@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>, Andrey Korolyov <andrey@xdel.ru>, Fam Zheng <famz@redhat.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, Marcelo Tosatti <mtosatti@redhat.com>

W dniu 2014-07-18 11:37, Paolo Bonzini pisze:
> Il 18/07/2014 11:32, Marcin Gibu=C5=82a ha scritto:
>>
>>> 3) the next CPU entry will call kvm_arch_put_registers:
>>>
>>>          if (cpu->kvm_vcpu_dirty) {
>>>              kvm_arch_put_registers(cpu, KVM_PUT_RUNTIME_STATE);
>>>              cpu->kvm_vcpu_dirty =3D false;
>>>          }
>>
>> But, I don't set cpu->kvm_vcpu_dirty anywhere (?).
>
> Yeah, the next CPU entry will *not* call kvm_arch_put_registers with
> your change.  It will call it with vanilla cpu_synchronize_all_states()=
.

That's because in kvmclock, it's used only to read cpu registers, not=20
edit them.

Now, because making this call "invisible" makes it work, I'm speculating=20
that following happens:

[migration starts]
kvmclock: calls cpu_synchronize_all_states()
somewhere in qemu: completes IO
somewhere in qemu: calls cpu_synchronize_all_states() <- old state


Is it (or something similar) possible? I didn't dig deep enough into=20
internals yet, but perhaps you could point if thats the right direction?

--=20
mg