From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Manos Pitsidianakis <el13635@mail.ntua.gr>,
qemu-devel <qemu-devel@nongnu.org>,
Alberto Garcia <berto@igalia.com>,
qemu-block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 3/3] block: remove legacy I/O throttling
Date: Wed, 2 Aug 2017 12:33:19 +0200 [thread overview]
Message-ID: <20170802103319.GB3649@localhost.localdomain> (raw)
In-Reply-To: <20170802100724.GD5531@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1926 bytes --]
Am 02.08.2017 um 12:07 hat Stefan Hajnoczi geschrieben:
> On Tue, Aug 01, 2017 at 04:49:07PM +0300, Manos Pitsidianakis wrote:
> > diff --git a/block.c b/block.c
> > index 9ebdba28b0..c6aad25286 100644
> > --- a/block.c
> > +++ b/block.c
> > @@ -1975,6 +1975,7 @@ BdrvChild *bdrv_root_attach_child(BlockDriverState *child_bs,
> > child = g_new(BdrvChild, 1);
> > *child = (BdrvChild) {
> > .bs = NULL,
> > + .parent_bs = NULL,
> > .name = g_strdup(child_name),
> > .role = child_role,
> > .perm = perm,
> > @@ -2009,6 +2010,7 @@ BdrvChild *bdrv_attach_child(BlockDriverState *parent_bs,
> > if (child == NULL) {
> > return NULL;
> > }
> > + child->parent_bs = parent_bs;
> >
> > QLIST_INSERT_HEAD(&parent_bs->children, child, next);
> > return child;
> > @@ -3729,6 +3731,12 @@ const char *bdrv_get_parent_name(const BlockDriverState *bs)
> > return name;
> > }
> > }
> > + if (c->parent_bs && c->parent_bs->implicit) {
> > + name = bdrv_get_parent_name(c->parent_bs);
> > + if (name && *name) {
> > + return name;
> > + }
> > + }
> > }
> >
> > return NULL;
>
> This should be a separate patch.
>
> Who updates parent_bs if the parent is changed (e.g.
> bdrv_replace_node())?
>
> We already have bs->parents. Why is BdrvChild->parent_bs needed?
I haven't look at the whole patch yet, but BdrvChild->parent_bs is a
thing that intentionally doesn't exist. A node simply has no business
knowing its parents - which may or may not be BlockDriverStates (the
obvious example where they aren't BDSes are BlockBackends, but block
jobs own some BdrvChild objects, too).
Usually the replacement is a BdrvChildRole callback.
Kevin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-08-02 10:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 13:49 [Qemu-devel] [PATCH 0/3] block: remove legacy I/O throttling Manos Pitsidianakis
2017-08-01 13:49 ` [Qemu-devel] [PATCH 1/3] block: add options parameter to bdrv_new_open_driver() Manos Pitsidianakis
2017-08-02 9:33 ` Stefan Hajnoczi
2017-08-01 13:49 ` [Qemu-devel] [PATCH 2/3] block: skip implicit nodes in snapshots, blockjobs Manos Pitsidianakis
2017-08-02 9:52 ` Stefan Hajnoczi
2017-08-03 10:22 ` Kevin Wolf
2017-08-01 13:49 ` [Qemu-devel] [PATCH 3/3] block: remove legacy I/O throttling Manos Pitsidianakis
2017-08-02 10:07 ` Stefan Hajnoczi
2017-08-02 10:33 ` Kevin Wolf [this message]
2017-08-02 16:46 ` Manos Pitsidianakis
2017-08-02 10:34 ` Manos Pitsidianakis
2017-08-02 14:36 ` Stefan Hajnoczi
2017-08-03 11:10 ` Kevin Wolf
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=20170802103319.GB3649@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=berto@igalia.com \
--cc=el13635@mail.ntua.gr \
--cc=qemu-block@nongnu.org \
--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).