From: Max Reitz <mreitz@redhat.com>
To: Alberto Garcia <berto@igalia.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] throttle: test that snapshots move the throttling configuration
Date: Fri, 18 Sep 2015 17:54:36 +0200 [thread overview]
Message-ID: <55FC33BC.5080803@redhat.com> (raw)
In-Reply-To: <1442500386-3668-1-git-send-email-berto@igalia.com>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
On 17.09.2015 16:33, Alberto Garcia wrote:
> If a snapshot is performed on a device that has I/O limits they should
> be moved to the target image (the new active layer).
>
> Signed-off-by: Alberto Garcia <berto@igalia.com>
> ---
> tests/qemu-iotests/096 | 69 ++++++++++++++++++++++++++++++++++++++++++++++
> tests/qemu-iotests/096.out | 5 ++++
> tests/qemu-iotests/group | 1 +
> 3 files changed, 75 insertions(+)
> create mode 100644 tests/qemu-iotests/096
> create mode 100644 tests/qemu-iotests/096.out
Looks good, I'd just like to throw in that 096 is in use by my
looks-dead-but-actually-is-not and
only-waiting-for-the-blockbackend-and-media-series-to-get-merged series
"block: Rework bdrv_close_all()":
http://lists.nongnu.org/archive/html/qemu-block/2015-03/msg00048.html
But then again, once the prerequisites are met, I'll have to send a new
version of that series anyway...
So, since 096 is not a magic number I'm extremely keen on keeping in my
greedy claws:
Reviewed-by: Max Reitz <mreitz@redhat.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-09-18 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 14:33 [Qemu-devel] [PATCH] throttle: test that snapshots move the throttling configuration Alberto Garcia
2015-09-18 15:54 ` Max Reitz [this message]
2015-09-21 7:02 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2015-10-06 15:09 ` Kevin Wolf
2015-10-06 14:16 ` [Qemu-devel] " Alberto Garcia
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=55FC33BC.5080803@redhat.com \
--to=mreitz@redhat.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.