From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Eric Blake <eblake@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Fam Zheng <famz@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>,
peterx@redhat.com
Subject: [Qemu-devel] [PATCH 0/4] qtest: fix "device_del" out-of-order events
Date: Wed, 13 Sep 2017 17:36:02 +0800 [thread overview]
Message-ID: <1505295366-25295-1-git-send-email-peterx@redhat.com> (raw)
It starts from a "make check" failure on one of my private tree. The
problem is that when we do "device_del" we normally looking for two
things: one response (which is mostly empty), and a REMOVE event. The
tricky point is the event can either be there before/after the empty
response. So I added qmp_device_del() to make sure the order does not
matter, then use it where proper.
Since I'm at it, I also added the sister helper qmp_device_add(), it
helps to remove LOCs.
I still don't 100% sure why my private tree can trigger this error,
while the master cannot. Anyway, I think this is something we should
have, no matter what.
Please review. Thanks.
Peter Xu (4):
libqtest: add qmp_device_del()
tests: use qmp_device_del() where proper
libqtest: add qmp_device_add()
tests: use qmp_device_add() where proper
tests/libqos/pci.c | 15 +++--------
tests/libqos/usb.c | 28 +++++----------------
tests/libqtest.c | 63 +++++++++++++++++++++++++++++++++++++++++++++++
tests/libqtest.h | 17 +++++++++++++
tests/usb-hcd-uhci-test.c | 28 +++------------------
tests/usb-hcd-xhci-test.c | 52 ++++----------------------------------
6 files changed, 97 insertions(+), 106 deletions(-)
--
2.7.4
next reply other threads:[~2017-09-13 9:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 9:36 Peter Xu [this message]
2017-09-13 9:36 ` [Qemu-devel] [PATCH 1/4] libqtest: add qmp_device_del() Peter Xu
2017-10-02 17:25 ` Markus Armbruster
2017-10-02 17:33 ` Eric Blake
2017-09-13 9:36 ` [Qemu-devel] [PATCH 2/4] tests: use qmp_device_del() where proper Peter Xu
2017-09-13 9:36 ` [Qemu-devel] [PATCH 3/4] libqtest: add qmp_device_add() Peter Xu
2017-09-13 10:01 ` Thomas Huth
2017-09-13 9:36 ` [Qemu-devel] [PATCH 4/4] tests: use qmp_device_add() where proper Peter Xu
2017-09-13 9:53 ` [Qemu-devel] [PATCH 0/4] qtest: fix "device_del" out-of-order events Thomas Huth
2017-09-13 10:28 ` Peter Xu
2017-09-13 10:35 ` Thomas Huth
2017-09-13 10:42 ` Peter Xu
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=1505295366-25295-1-git-send-email-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@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 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.