From: Amos Kong <akong@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
arei.gonglei@huawei.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 0/4] test virtio-blk hotplug
Date: Wed, 18 Jun 2014 13:46:39 +0800 [thread overview]
Message-ID: <20140618054639.GB32372@z.redhat.com> (raw)
In-Reply-To: <20140618025852.GA32372@z.redhat.com>
On Wed, Jun 18, 2014 at 10:58:52AM +0800, Amos Kong wrote:
> On Tue, Jun 17, 2014 at 03:37:08PM +0200, Andreas Färber wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Hi Amos,
> >
> > Am 17.06.2014 14:54, schrieb Amos Kong:
> > > On Mon, Jun 09, 2014 at 03:22:51PM +0200, Stefan Hajnoczi wrote:
> > >> On Fri, Jun 06, 2014 at 10:33:49PM +0800, Amos Kong wrote:
> > >>> It's worth to add a hotplug test to qtest, but without
> > >>> cooperation of guest OS, new devices can't be initialized by
> > >>> guest, and hot-unplug doesn't work.
> > >>>
> > >>> However, the new test can cover some part of code of
> > >>> hotplug/unplug.
> > >>>
> > >>> I will write another subtest to test hotplug with pci support.
> > >>>
> > >>> V2: move qmp_exec_hmp_cmd() to libqtest.c excape hmp cmd
> > >>> (stefanha) use qmp_exec_hmp_cmd() in blockdev-test V3: use
> > >>> vp_list to format string, free escaped string V4: free escaped
> > >>> string by g_free()
> > >
> > > Hi Andreas,
> > >
> > > Can you apply this patchset to your tree?
> >
> > Sorry for the late reply, I was on vacation and am still fighting a
> > mail backlog...
>
> That's OK :)
>
> > I had a question about the new HMP helper function - I see in 4/4 that
> > drive_add was already being done via HMP, so I guess that's the
> > culprit, but still I wonder whether we can do device-add via QMP.
>
> I didn't find device_add/del definition in qapi-schema.json, so I
> used HMP instead. Actually those two QMP commands exist and work.
>
> { "execute": "blockdev-add", "arguments": { "options": { "driver":
> "file", "filename": "/dev/null", "id": "id1" } } }
>
> { "execute": "device_add", "arguments": { "driver": "virtio-blk-pci",
> "drive": "id1", "driver": "virtio-blk-pci", "id": "id2" } }
>
> I will convert virtio-blk-test to use QMP, send a V5.
We have QMP command to hot-unplug device:
{ "execute": "device_del", "arguments": { "id": "id2" } }
But there is not QMP command to hot-unplug drive/blockdev
drive_del / blockdev-del doesn't exist, so I will use
human-monitor-command to hot-unplug blockdev.
> > That said, I've reviewed the generic qtest part OK, and would assume
> > virtio-blk-test (you can drop the .c in the topic please) to go
> > through the same tree virtio-blk does, so via Stefan/Kevin.
>
> Stefan said (offline) it belongs to you, and I found the first commit of
> this file was merged by you.
>
> Thanks.
>
> > Regards,
> > Andreas
>
> --
> Amos.
--
Amos.
prev parent reply other threads:[~2014-06-18 5:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 14:33 [Qemu-devel] [PATCH v4 0/4] test virtio-blk hotplug Amos Kong
2014-06-06 14:33 ` [Qemu-devel] [PATCH v4 1/4] virtio-blk-test.c: change pci_nop() to virtblk_init() Amos Kong
2014-06-06 14:33 ` [Qemu-devel] [PATCH v4 2/4] qtest: introduce qmp_exec_hmp_cmd() Amos Kong
2014-06-17 13:16 ` Andreas Färber
2014-06-17 17:37 ` Paolo Bonzini
2014-06-18 6:29 ` Amos Kong
2014-06-18 7:05 ` Paolo Bonzini
2014-06-06 14:33 ` [Qemu-devel] [PATCH v4 3/4] virtio-blk-test.c: add hotplug subtest Amos Kong
2014-06-17 13:25 ` Andreas Färber
2014-06-18 6:40 ` Amos Kong
2014-06-18 10:26 ` Andreas Färber
2014-06-06 14:33 ` [Qemu-devel] [PATCH v4 4/4] qtest: use qmp_exec_hmp_cmd() in blockdev-test Amos Kong
2014-06-17 13:28 ` Andreas Färber
2014-06-09 13:22 ` [Qemu-devel] [PATCH v4 0/4] test virtio-blk hotplug Stefan Hajnoczi
2014-06-17 12:54 ` Amos Kong
2014-06-17 13:37 ` Andreas Färber
2014-06-18 2:58 ` Amos Kong
2014-06-18 3:04 ` Stefan Hajnoczi
2014-06-18 5:46 ` Amos Kong [this message]
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=20140618054639.GB32372@z.redhat.com \
--to=akong@redhat.com \
--cc=afaerber@suse.de \
--cc=arei.gonglei@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).