From: Stefan Hajnoczi <stefanha@gmail.com>
To: Amos Kong <akong@redhat.com>
Cc: mst@redhat.com, qemu-devel@nongnu.org, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v2 3/4] virtio-blk-test.c: add hotplug subtest
Date: Thu, 5 Jun 2014 11:31:28 +0200 [thread overview]
Message-ID: <20140605093128.GG27366@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1401947118-19973-4-git-send-email-akong@redhat.com>
On Thu, Jun 05, 2014 at 01:45:17PM +0800, Amos Kong wrote:
> This patch adds a new subtest, it hotplugs 29 * 8 = 232 virtio-blk
> devices to guest, and try to hot-unplug them.
>
> Note: the hot-unplug can't work without cooperation of guest OS.
>
> Signed-off-by: Amos Kong <akong@redhat.com>
> ---
> tests/virtio-blk-test.c | 38 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 38 insertions(+)
>
> diff --git a/tests/virtio-blk-test.c b/tests/virtio-blk-test.c
> index 0fdec01..616599a 100644
> --- a/tests/virtio-blk-test.c
> +++ b/tests/virtio-blk-test.c
> @@ -7,11 +7,48 @@
> * See the COPYING file in the top-level directory.
> */
>
> +#include <stdio.h>
> #include <glib.h>
> #include <string.h>
> #include "libqtest.h"
> #include "qemu/osdep.h"
>
> +static void test_blk_hotplug(void)
> +{
> + char addr[6];
> + char cmd[100];
> + int i, j;
> +
> + /* start with no network/block device, slots 3~0x1f are free */
> + qtest_start("-net none");
> +
> + for (i = 3; i <= 0x1f; i++) {
> + for (j = 7; j >= 0; j--) {
> + sprintf(addr, "%x.%x", i, j);
> + sprintf(cmd, "drive_add 0 if=none,file=/dev/null,id=drv-%s", addr);
> + qmp_exec_hmp_cmd(cmd, "OK\r\n");
> +
> + sprintf(cmd, "device_add virtio-blk-pci,id=dev-%s,drive=drv-%s,"
> + "addr=0x%s,multifunction=on", addr, addr, addr);
> + qmp_exec_hmp_cmd(cmd, "");
> + }
> + }
> +
> + /* hot-unplug doesn't work without cooperation of guest OS */
> + for (i = 3; i <= 0x1f; i++) {
> + for (j = 7; j >= 0; j--) {
> + sprintf(addr, "%x.%x", i, j);
> + sprintf(cmd, "drive_del drv-%s", addr);
> + qmp_exec_hmp_cmd(cmd, "");
> +
> + sprintf(cmd, "device_del dev-%s", addr);
> + qmp_exec_hmp_cmd(cmd, "");
> + }
> + }
All of this sprintf() usage makes me wonder about:
qmp_exec_hmp_cmd(const char *expected_ret, const char *fmt, ...);
This way callers don't need to manage formatting buffers themselves.
Besides that:
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
next prev parent reply other threads:[~2014-06-05 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 5:45 [Qemu-devel] [PATCH v2 0/4] test virtio-blk hotplug Amos Kong
2014-06-05 5:45 ` [Qemu-devel] [PATCH v2 1/4] virtio-blk-test.c: change pci_nop() to virtblk_init() Amos Kong
2014-06-05 5:45 ` [Qemu-devel] [PATCH v2 2/4] qtest: introduce qmp_exec_hmp_cmd() Amos Kong
2014-06-05 7:16 ` Gonglei (Arei)
2014-06-05 9:29 ` Stefan Hajnoczi
2014-06-05 5:45 ` [Qemu-devel] [PATCH v2 3/4] virtio-blk-test.c: add hotplug subtest Amos Kong
2014-06-05 9:31 ` Stefan Hajnoczi [this message]
2014-06-05 5:45 ` [Qemu-devel] [PATCH v2 4/4] qtest: use qmp_exec_hmp_cmd() in blockdev-test Amos Kong
2014-06-05 9:32 ` 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=20140605093128.GG27366@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=afaerber@suse.de \
--cc=akong@redhat.com \
--cc=mst@redhat.com \
--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).