qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Wen Congyang <wency@cn.fujitsu.com>,
	Wen Congyang <ghostwcy@gmail.com>,
	qemu-devl <qemu-devel@nongnu.org>, Jeff Cody <jcody@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
	qemu-block@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] refresh filename after the node is replaced
Date: Wed, 1 Jul 2015 17:15:24 +0200	[thread overview]
Message-ID: <5594040C.8080306@redhat.com> (raw)
In-Reply-To: <55933DA0.8050805@cn.fujitsu.com>

On 01.07.2015 03:08, Wen Congyang wrote:
> On 06/30/2015 09:17 PM, Max Reitz wrote:
>> On 29.06.2015 03:16, Wen Congyang wrote:
>>> On 06/26/2015 11:16 PM, Max Reitz wrote:
>>>> I see two solutions to this issue: Either, we do it right and that means, if there is a change in the BDS graph (e.g. because of bdrv_swap()),
>>>> we have to call bdrv_refresh_filename() on all of the changed BDS's parents. In order to be able to enumerate a BDS's parents, we need Kevin's
>>>> series, as said before.
>>> IIUC, the BDS can have more than one parent.
>> Indeed. Kevin's series adds a generalized parent-child relationship, which makes it possible to both enumerate all the children of a BDS and all its parents.
> How to get all its parents? Is this patch not merged into upstream?

The patch is actually already merged upstream 
(6e93e7c41fdfdee3068770cae79380e1d986b76a), but it does not add a way to 
enumerate a BDS's parents, only a BDS's children. It should not be too 
difficult to implement the reverse however, I guess, based on that patch.
Konsole output
>>>> Or we revive my series "block: Drop BDS.filename" which drops the BDS.filename field completely and always rebuilds it if it is queried.
>>>> This would fix the issue as well, however, there is a reason it has been lying around for nine months now, and that reason is that we did
>>>> not yet fully examine the impacts of dropping that field, especially concerning libvirt.
>>> If BDS.filename is dropped, this problem will go.
>> Right. But we have to make sure there won't be any negative impact if we do so, and because that is not really trivial, the series hasn't been applied yet and didn't receive further attention. Also, there was no real reason to do it other than "Because we can" until now. But I think the issue mentioned here is a good reason why we should indeed reconsider it.
> I don't find this series.

Maybe because it's pretty old. :-) I sent it last September: 
http://lists.nongnu.org/archive/html/qemu-devel/2014-09/msg04878.html

Max

      reply	other threads:[~2015-07-01 15:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25  6:41 [Qemu-devel] [PATCH] refresh filename after the node is replaced Wen Congyang
2015-06-26 13:47 ` Max Reitz
2015-06-26 14:27   ` Wen Congyang
2015-06-26 15:16     ` Max Reitz
2015-06-29  1:16       ` Wen Congyang
2015-06-30 13:17         ` Max Reitz
2015-07-01  1:08           ` Wen Congyang
2015-07-01 15:15             ` Max Reitz [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=5594040C.8080306@redhat.com \
    --to=mreitz@redhat.com \
    --cc=famz@redhat.com \
    --cc=ghostwcy@gmail.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=wency@cn.fujitsu.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).