From: benoit.canet@gmail.com
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, "Benoît Canet" <benoit@irqsave.net>,
lcapitulino@redhat.com, pbonzini@redhat.com, eblake@redhat.com,
stefanha@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH V4 0/3] Show backing file depth in HMP
Date: Thu, 26 Jul 2012 13:16:03 +0200 [thread overview]
Message-ID: <1343301366-18028-1-git-send-email-benoit@irqsave.net> (raw)
From: Benoît Canet <benoit@irqsave.net>
In some setups many backing files and snapshot are chained.
This lead to the formation of huge trees of snapshots all depending
on a common ancestor.
Hence if something bad happen to this common ancestor all the snapshot
of the tree will be broken.
This patch add an easy way for the user to monitor backing file depth
and take the good decision (streaming).
in v2:
lcapitulino: -Fix typo in qapi-schema.json
-rename *file_ancestors_count to
*backing_file_ancestor_count
in v3:
kwolf: qapi-schema.json backing_file_ancestor_count field not optional
Add a (since 1.2) comment
keep display in HMP optional
in v4:
eblake: rename backing_file.ancestors.count to backing.file.depth
in qapi-schema.json use - instead of _
Fix json docstring
Benoît Canet (3):
block: create bdrv_get_backing_file_depth()
block: Use bdrv_get_backing_file_depth()
hmp: show the backing file depth
block.c | 16 ++++++++++++++++
block.h | 1 +
hmp.c | 2 ++
qapi-schema.json | 9 ++++++---
4 files changed, 25 insertions(+), 3 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-07-26 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 11:16 benoit.canet [this message]
2012-07-26 11:16 ` [Qemu-devel] [PATCH V4 1/3] block: create bdrv_get_backing_file_depth() benoit.canet
2012-07-26 11:16 ` [Qemu-devel] [PATCH V4 2/3] block: Use bdrv_get_backing_file_depth() benoit.canet
2012-07-26 12:30 ` Eric Blake
2012-07-26 11:16 ` [Qemu-devel] [PATCH V4 3/3] hmp: show the backing file depth benoit.canet
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=1343301366-18028-1-git-send-email-benoit@irqsave.net \
--to=benoit.canet@gmail.com \
--cc=benoit@irqsave.net \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).