From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33939) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqOGf-0003My-LN for qemu-devel@nongnu.org; Mon, 17 Nov 2014 10:31:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XqOGZ-0004JR-E9 for qemu-devel@nongnu.org; Mon, 17 Nov 2014 10:31:05 -0500 Received: from mx1.redhat.com ([209.132.183.28]:36329) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqOGZ-0004J7-7v for qemu-devel@nongnu.org; Mon, 17 Nov 2014 10:30:59 -0500 From: Max Reitz Date: Mon, 17 Nov 2014 16:30:45 +0100 Message-Id: <1416238250-414-1-git-send-email-mreitz@redhat.com> Subject: [Qemu-devel] [PATCH 0/5] nbd: Use BlockBackend List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Kevin Wolf , Peter Lieven , Markus Armbruster , Max Reitz , Stefan Hajnoczi , Paolo Bonzini >>From the block layer's perspective, the nbd server is pretty similar to a guest device. Therefore, it should use BlockBackend to access block devices, just like any other guest device does. This series consequently makes the nbd server use BlockBackend for referencing block devices. Max Reitz (5): block: Lift more functions into BlockBackend block: Add AioContextNotifier functions to BB block: Add blk_add_close_notifier() for BB nbd: Change external interface to BlockBackend nbd: Use BlockBackend internally block/block-backend.c | 38 +++++++++++++++++++++++++ blockdev-nbd.c | 15 +++++----- include/block/nbd.h | 7 ++--- include/sysemu/block-backend.h | 12 ++++++++ nbd.c | 63 +++++++++++++++++++++--------------------- qemu-nbd.c | 2 +- 6 files changed, 94 insertions(+), 43 deletions(-) -- 1.9.3