[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v3 02/23] block: New BlockBackend
From: |
Kevin Wolf |
Subject: |
Re: [Qemu-devel] [PATCH v3 02/23] block: New BlockBackend |
Date: |
Fri, 19 Sep 2014 18:17:27 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Am 16.09.2014 um 20:12 hat Markus Armbruster geschrieben:
> A block device consists of a frontend device model and a backend.
>
> A block backend has a tree of block drivers doing the actual work.
> The tree is managed by the block layer.
>
> We currently use a single abstraction BlockDriverState both for tree
> nodes and the backend as a whole. Drawbacks:
>
> * Its API includes both stuff that makes sense only at the block
> backend level (root of the tree) and stuff that's only for use
> within the block layer. This makes the API bigger and more complex
> than necessary. Moreover, it's not obvious which interfaces are
> meant for device models, and which really aren't.
>
> * Since device models keep a reference to their backend, the backend
> object can't just be destroyed. But for media change, we need to
> replace the tree. Our solution is to make the BlockDriverState
> generic, with actual driver state in a separate object, pointed to
> by member opaque. That lets us replace the tree by deinitializing
> and reinitializing its root. This special need of the root makes
> the data structure awkward everywhere in the tree.
>
> The general plan is to separate the APIs into "block backend", for use
> by device models, monitor and whatever other code dealing with block
> backends, and "block driver", for use by the block layer and whatever
> other code (if any) dealing with trees and tree nodes.
>
> Code dealing with block backends, device models in particular, should
> become completely oblivious of BlockDriverState. This should let us
> clean up both APIs, and the tree data structures.
>
> This commit is a first step. It creates a minimal "block backend"
> API: type BlockBackend and functions to create, destroy and find them.
>
> BlockBackend objects are created and destroyed exactly when root
> BlockDriverState objects are created and destroyed. "Root" in the
> sense of "in bdrv_states". They're not yet used for anything; that'll
> come shortly.
>
> BlockBackend is reference-counted. Its reference count never exceeds
> one so far, but that's going to change.
>
> Signed-off-by: Markus Armbruster <address@hidden>
> diff --git a/include/sysemu/block-backend.h b/include/sysemu/block-backend.h
> new file mode 100644
> index 0000000..3f8371c
> --- /dev/null
> +++ b/include/sysemu/block-backend.h
> @@ -0,0 +1,26 @@
> +/*
> + * QEMU Block backends
> + *
> + * Copyright (C) 2014 Red Hat, Inc.
> + *
> + * Authors:
> + * Markus Armbruster <address@hidden>,
> + *
> + * This work is licensed under the terms of the GNU GPL, version 2 or
> + * later. See the COPYING file in the top-level directory.
> + */
This one should be LGPL as well.
The distribution of blk_unref() should be good enough. To be correct it
requires the assumption that the blockdev-add reference to any given BDS
is the last one that goes away. I'm not sure if this is the case here (I
suspect it isn't), but at the end of the series, we should be good.
With the license fixed, you can add:
Reviewed-by Kevin Wolf <address@hidden>
Kevin
- Re: [Qemu-devel] [PATCH v3 03/23] block: Connect BlockBackend to BlockDriverState, (continued)
[Qemu-devel] [PATCH v3 05/23] block: Code motion to get rid of stubs/blockdev.c, Markus Armbruster, 2014/09/16
[Qemu-devel] [PATCH v3 09/23] block: Merge BlockBackend and BlockDriverState name spaces, Markus Armbruster, 2014/09/16
[Qemu-devel] [PATCH v3 02/23] block: New BlockBackend, Markus Armbruster, 2014/09/16
[Qemu-devel] [PATCH v3 07/23] block: Eliminate bdrv_iterate(), use bdrv_next(), Markus Armbruster, 2014/09/16
[Qemu-devel] [PATCH v3 10/23] block: Eliminate DriveInfo member bdrv, use blk_by_legacy_dinfo(), Markus Armbruster, 2014/09/16