From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, kwolf@redhat.com, eesposit@redhat.com
Subject: [RFC PATCH] test-bdrv-drain: keep graph manipulations out of coroutines
Date: Fri, 2 Dec 2022 14:27:01 +0100 [thread overview]
Message-ID: <20221202132701.531048-1-pbonzini@redhat.com> (raw)
Changes to the BlockDriverState graph will have to take the
corresponding lock for writing, and therefore cannot be done
inside a coroutine. Move them outside the test body.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
tests/unit/test-bdrv-drain.c | 63 ++++++++++++++++++++++++++----------
1 file changed, 46 insertions(+), 17 deletions(-)
diff --git a/tests/unit/test-bdrv-drain.c b/tests/unit/test-bdrv-drain.c
index 6ae44116fe79..d85083dd4f9e 100644
--- a/tests/unit/test-bdrv-drain.c
+++ b/tests/unit/test-bdrv-drain.c
@@ -199,25 +199,40 @@ static void do_drain_end_unlocked(enum drain_type drain_type, BlockDriverState *
}
}
+static BlockBackend *blk;
+static BlockDriverState *bs, *backing;
+
+static void test_drv_cb_init(void)
+{
+ blk = blk_new(qemu_get_aio_context(), BLK_PERM_ALL, BLK_PERM_ALL);
+ bs = bdrv_new_open_driver(&bdrv_test, "test-node", BDRV_O_RDWR,
+ &error_abort);
+ blk_insert_bs(blk, bs, &error_abort);
+
+ backing = bdrv_new_open_driver(&bdrv_test, "backing", 0, &error_abort);
+ bdrv_set_backing_hd(bs, backing, &error_abort);
+}
+
+static void test_drv_cb_fini(void)
+{
+ bdrv_unref(backing);
+ bdrv_unref(bs);
+ blk_unref(blk);
+ backing = NULL;
+ bs = NULL;
+ blk = NULL;
+}
+
static void test_drv_cb_common(enum drain_type drain_type, bool recursive)
{
- BlockBackend *blk;
- BlockDriverState *bs, *backing;
BDRVTestState *s, *backing_s;
BlockAIOCB *acb;
int aio_ret;
QEMUIOVector qiov = QEMU_IOVEC_INIT_BUF(qiov, NULL, 0);
- blk = blk_new(qemu_get_aio_context(), BLK_PERM_ALL, BLK_PERM_ALL);
- bs = bdrv_new_open_driver(&bdrv_test, "test-node", BDRV_O_RDWR,
- &error_abort);
s = bs->opaque;
- blk_insert_bs(blk, bs, &error_abort);
-
- backing = bdrv_new_open_driver(&bdrv_test, "backing", 0, &error_abort);
backing_s = backing->opaque;
- bdrv_set_backing_hd(bs, backing, &error_abort);
/* Simple bdrv_drain_all_begin/end pair, check that CBs are called */
g_assert_cmpint(s->drain_count, ==, 0);
@@ -252,30 +267,44 @@ static void test_drv_cb_common(enum drain_type drain_type, bool recursive)
g_assert_cmpint(s->drain_count, ==, 0);
g_assert_cmpint(backing_s->drain_count, ==, 0);
-
- bdrv_unref(backing);
- bdrv_unref(bs);
- blk_unref(blk);
}
-static void test_drv_cb_drain_all(void)
+static void test_drv_cb_do_drain_all(void)
{
test_drv_cb_common(BDRV_DRAIN_ALL, true);
}
-static void test_drv_cb_drain(void)
+static void test_drv_cb_do_drain(void)
{
test_drv_cb_common(BDRV_DRAIN, false);
}
+static void test_drv_cb_drain_all(void)
+{
+ test_drv_cb_init();
+ test_drv_cb_do_drain_all();
+ test_drv_cb_fini();
+}
+
+static void test_drv_cb_drain(void)
+{
+ test_drv_cb_init();
+ test_drv_cb_do_drain();
+ test_drv_cb_fini();
+}
+
static void test_drv_cb_co_drain_all(void)
{
- call_in_coroutine(test_drv_cb_drain_all);
+ test_drv_cb_init();
+ call_in_coroutine(test_drv_cb_do_drain_all);
+ test_drv_cb_fini();
}
static void test_drv_cb_co_drain(void)
{
- call_in_coroutine(test_drv_cb_drain);
+ test_drv_cb_init();
+ call_in_coroutine(test_drv_cb_do_drain);
+ test_drv_cb_fini();
}
static void test_quiesce_common(enum drain_type drain_type, bool recursive)
--
2.38.1
next reply other threads:[~2022-12-02 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 13:27 Paolo Bonzini [this message]
2022-12-02 13:42 ` [RFC PATCH] test-bdrv-drain: keep graph manipulations out of coroutines Emanuele Giuseppe Esposito
2022-12-02 17:22 ` Paolo Bonzini
2022-12-05 12:36 ` Emanuele Giuseppe Esposito
2022-12-05 13:01 ` Kevin Wolf
2022-12-09 12:18 ` Emanuele Giuseppe Esposito
2022-12-09 12:20 ` Emanuele Giuseppe Esposito
2022-12-09 19:34 ` 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=20221202132701.531048-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=eesposit@redhat.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 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).