From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=45455 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PIoxH-0006eY-3G for qemu-devel@nongnu.org; Wed, 17 Nov 2010 15:50:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PIoxG-0008Ni-0v for qemu-devel@nongnu.org; Wed, 17 Nov 2010 15:50:10 -0500 Received: from mx1.redhat.com ([209.132.183.28]:25394) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PIoxF-0008NE-Og for qemu-devel@nongnu.org; Wed, 17 Nov 2010 15:50:09 -0500 Date: Wed, 17 Nov 2010 22:49:52 +0200 From: "Michael S. Tsirkin" Subject: Re: [Qemu-devel] Re: [PATCH v4 0/4] virtio: Use ioeventfd for virtqueue notify Message-ID: <20101117204952.GA31717@redhat.com> References: <1290010769-11217-1-git-send-email-stefanha@linux.vnet.ibm.com> <20101117180142.GF29556@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Stefan Hajnoczi , qemu-devel@nongnu.org On Wed, Nov 17, 2010 at 08:38:25PM +0000, Stefan Hajnoczi wrote: > On Wed, Nov 17, 2010 at 6:01 PM, Michael S. Tsirkin wr= ote: > > On Wed, Nov 17, 2010 at 04:19:25PM +0000, Stefan Hajnoczi wrote: > >> The v4 version includes: > >> =A0* Simpler start/stop ioeventfd mechanism using bool ioeventfd_sta= rted state > >> =A0* Support for migration > >> =A0* Handle deassign race condition to avoid dropping a virtqueue ki= ck > >> =A0* Add missing kvm_enabled() check to kvm_has_many_ioeventfds() > >> =A0* Documentation updates for qdev -device with ioeventfd=3Don|off > > > > Anthony, could you pls remind me what did you say > > about need to stop these threads on migration vmstop? > > Or am I confusing this with something else? >=20 > Two points about the VM change state: > 1. It is used to bring up virtio-ioeventfd on the destination host > after migration. > 2. It handles the race condition where a virtqueue kick is dropped > because we deassign the ioeventfd on the source host. >=20 > So I've implemented the VM change state to get correct migration behavi= or. >=20 > The discussion you had with Anthony was more about events happening > while the VM is paused and how that could interfere with guest state > for migration IIRC. >=20 > Stefan Exactly. Could your patches cause a situation where block virtio ring is used after migration stopped a VM? --=20 MST