From: Stefan Hajnoczi <stefanha@gmail.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/6] nbd: Use BlockBackend
Date: Wed, 26 Nov 2014 16:19:42 +0000 [thread overview]
Message-ID: <20141126161942.GE14288@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1416309679-333-1-git-send-email-mreitz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2003 bytes --]
On Tue, Nov 18, 2014 at 12:21:13PM +0100, Max Reitz wrote:
> 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.
>
>
> v2:
> - Added patch 6, which converts qemu-nbd to BlockBackend as far as
> reasonable [Paolo]
>
>
> git-backport-diff against v1:
>
> Key:
> [----] : patches are identical
> [####] : number of functional differences between upstream/downstream patch
> [down] : patch is downstream-only
> The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
>
> 001/6:[----] [--] 'block: Lift more functions into BlockBackend'
> 002/6:[----] [--] 'block: Add AioContextNotifier functions to BB'
> 003/6:[----] [--] 'block: Add blk_add_close_notifier() for BB'
> 004/6:[----] [--] 'nbd: Change external interface to BlockBackend'
> 005/6:[----] [--] 'nbd: Use BlockBackend internally'
> 006/6:[down] 'qemu-nbd: Use BlockBackend where reasonable'
>
>
> Max Reitz (6):
> 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
> qemu-nbd: Use BlockBackend where reasonable
>
> 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 | 12 ++++----
> 6 files changed, 99 insertions(+), 48 deletions(-)
>
> --
> 1.9.3
>
>
Thanks, applied to my block-next tree:
https://github.com/stefanha/qemu/commits/block-next
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2014-11-26 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 11:21 [Qemu-devel] [PATCH v2 0/6] nbd: Use BlockBackend Max Reitz
2014-11-18 11:21 ` [Qemu-devel] [PATCH v2 1/6] block: Lift more functions into BlockBackend Max Reitz
2014-11-18 11:21 ` [Qemu-devel] [PATCH v2 2/6] block: Add AioContextNotifier functions to BB Max Reitz
2014-11-18 11:21 ` [Qemu-devel] [PATCH v2 3/6] block: Add blk_add_close_notifier() for BB Max Reitz
2014-11-18 11:21 ` [Qemu-devel] [PATCH v2 4/6] nbd: Change external interface to BlockBackend Max Reitz
2014-11-18 11:21 ` [Qemu-devel] [PATCH v2 5/6] nbd: Use BlockBackend internally Max Reitz
2014-11-18 11:21 ` [Qemu-devel] [PATCH v2 6/6] qemu-nbd: Use BlockBackend where reasonable Max Reitz
2014-11-18 12:22 ` Paolo Bonzini
2014-11-26 16:19 ` Stefan Hajnoczi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141126161942.GE14288@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).