From: Peter Lieven <pl@kamp.de>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, mreitz@redhat.com,
Peter Lieven <pl@kamp.de>
Subject: [Qemu-devel] [RFC PATCH] qemu-io: add drain/undrain cmd
Date: Mon, 15 May 2017 12:02:43 +0200 [thread overview]
Message-ID: <1494842563-6534-1-git-send-email-pl@kamp.de> (raw)
Hi Block developers,
I would like to add a feature to Qemu to drain all traffic from a block so that
I can take external snaphosts without the risk to that in the middle of a write
operation. Its meant for cases where where QGA freeze/thaw is not available.
For me its enough to have this through qemu-io, but Kevin asked me to check
if its not worth to have a stable API for it and present it via QMP/HMP.
What are your thoughts?
Thanks,
Peter
---
qemu-io-cmds.c | 78 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 78 insertions(+)
diff --git a/qemu-io-cmds.c b/qemu-io-cmds.c
index 312fc6d..49d82fe 100644
--- a/qemu-io-cmds.c
+++ b/qemu-io-cmds.c
@@ -1565,6 +1565,82 @@ static const cmdinfo_t flush_cmd = {
.oneline = "flush all in-core file state to disk",
};
+static const cmdinfo_t drain_cmd;
+
+static int drain_f(BlockBackend *blk, int argc, char **argv)
+{
+ BlockDriverState *bs = blk_bs(blk);
+ bool flush = false;
+ int c;
+
+ while ((c = getopt(argc, argv, "f")) != -1) {
+ switch (c) {
+ case 'f':
+ flush = true;
+ break;
+ default:
+ return qemuio_command_usage(&drain_cmd);
+ }
+ }
+
+ if (optind != argc) {
+ return qemuio_command_usage(&drain_cmd);
+ }
+
+
+ if (bs->quiesce_counter) {
+ printf("drain failed: device is already drained!\n");
+ return 1;
+ }
+
+ bdrv_drained_begin(bs); /* complete I/O */
+ if (flush) {
+ bdrv_flush(bs);
+ bdrv_drain(bs); /* in case flush left pending I/O */
+ printf("flushed all pending I/O\n");
+ }
+ printf("drain successful\n");
+ return 0;
+}
+
+static void drain_help(void)
+{
+ printf(
+"\n"
+" Drains all external I/O from the device\n"
+"\n"
+" -f, -- flush all in-core file state to disk\n"
+"\n");
+}
+
+static const cmdinfo_t drain_cmd = {
+ .name = "drain",
+ .cfunc = drain_f,
+ .args = "[-f]",
+ .argmin = 0,
+ .argmax = -1,
+ .oneline = "cease to send I/O to the device",
+ .help = drain_help
+};
+
+static int undrain_f(BlockBackend *blk, int argc, char **argv)
+{
+ BlockDriverState *bs = blk_bs(blk);
+ if (!bs->quiesce_counter) {
+ printf("undrain failed: device is not drained!\n");
+ return 1;
+ }
+ bdrv_drained_end(bs);
+ printf("undrain successful\n");
+ return 0;
+}
+
+static const cmdinfo_t undrain_cmd = {
+ .name = "undrain",
+ .cfunc = undrain_f,
+ .oneline = "continue I/O to a drained device",
+};
+
static int truncate_f(BlockBackend *blk, int argc, char **argv)
{
int64_t offset;
@@ -2296,6 +2372,8 @@ static void __attribute((constructor)) init_qemuio_commands(void)
qemuio_add_command(&aio_write_cmd);
qemuio_add_command(&aio_flush_cmd);
qemuio_add_command(&flush_cmd);
+ qemuio_add_command(&drain_cmd);
+ qemuio_add_command(&undrain_cmd);
qemuio_add_command(&truncate_cmd);
qemuio_add_command(&length_cmd);
qemuio_add_command(&info_cmd);
--
1.9.1
next reply other threads:[~2017-05-15 10:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 10:02 Peter Lieven [this message]
2017-05-15 10:50 ` [Qemu-devel] [RFC PATCH] qemu-io: add drain/undrain cmd Fam Zheng
2017-05-15 11:26 ` Peter Lieven
2017-05-15 11:53 ` Fam Zheng
2017-05-15 11:58 ` Peter Lieven
2017-05-15 12:28 ` Fam Zheng
2017-05-15 12:32 ` Peter Lieven
2017-05-15 12:52 ` Fam Zheng
2017-05-15 13:01 ` Peter Lieven
2017-05-15 13:35 ` Fam Zheng
2017-05-15 14:02 ` Peter Lieven
2017-05-15 14:11 ` Fam Zheng
2017-05-15 13:02 ` Kevin Wolf
2017-05-15 14:23 ` Peter Lieven
2017-05-17 12:10 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
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=1494842563-6534-1-git-send-email-pl@kamp.de \
--to=pl@kamp.de \
--cc=kwolf@redhat.com \
--cc=mreitz@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 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).