From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=49783 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PE4Ac-0000Tz-TE for qemu-devel@nongnu.org; Thu, 04 Nov 2010 14:04:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PE4Ab-0003sX-Nw for qemu-devel@nongnu.org; Thu, 04 Nov 2010 14:04:18 -0400 Received: from mx1.redhat.com ([209.132.183.28]:28837) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PE4Ab-0003sO-Gt for qemu-devel@nongnu.org; Thu, 04 Nov 2010 14:04:17 -0400 Date: Thu, 4 Nov 2010 20:04:06 +0200 From: "Michael S. Tsirkin" Message-ID: <20101104180406.GA2820@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Qemu-devel] [PATCHv2 0/2] migration: stop dma while VM is stopped List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori , qemu-devel@nongnu.org Here's a patch that's much smaller: instead of trying to solve the whole problem, it fixes the specific bug I observe, that of net device traffic when vm is stopped confusing the bridge. We can then slowly convert all other devices that need to be stopped on vmstop to this API. Comments? Michael S. Tsirkin (2): char: separate device and system fd handlers tap: mark fd handler as device hw/vhost_net.c | 2 +- net/tap.c | 3 +- qemu-char.h | 6 ++- qemu-kvm.c | 2 +- qemu-tool.c | 10 +++++ vl.c | 117 ++++++++++++++++++++++++++++++++++++------------------- 6 files changed, 95 insertions(+), 45 deletions(-) -- 1.7.3.2.91.g446ac