From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57730) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XJNMa-0007LD-AM for qemu-devel@nongnu.org; Mon, 18 Aug 2014 09:52:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XJNMU-0002KX-6e for qemu-devel@nongnu.org; Mon, 18 Aug 2014 09:52:44 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39829) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XJNMT-0002Jj-UU for qemu-devel@nongnu.org; Mon, 18 Aug 2014 09:52:38 -0400 From: Stefan Hajnoczi Date: Mon, 18 Aug 2014 14:52:27 +0100 Message-Id: <1408369949-3128-1-git-send-email-stefanha@redhat.com> Subject: [Qemu-devel] [PATCH 0/2] block: support block_resize with dataplane List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Kevin Wolf , Andrey Korolyov , Stefan Hajnoczi , Max Reitz We have the op blocker and AioContext acquire/release infrastructure to safely allow block monitor commands on dataplane commands. It is now easy to make block_resize safe. Stefan Hajnoczi (2): block: acquire AioContext in qmp_block_resize() virtio-blk: allow block_resize with dataplane blockdev.c | 13 ++++++++++--- hw/block/dataplane/virtio-blk.c | 1 + 2 files changed, 11 insertions(+), 3 deletions(-) -- 1.9.3