From: Laurent Vivier <lvivier@redhat.com>
To: qemu-devel@nongnu.org
Cc: dgibson@redhat.com, thuth@redhat.com, qemu-ppc@nongnu.org,
Greg Kurz <groug@kaod.org>, Laurent Vivier <lvivier@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/5] tests: enable virtio tests on SPAPR
Date: Sat, 1 Oct 2016 20:55:59 +0200 [thread overview]
Message-ID: <1475348164-8593-1-git-send-email-lvivier@redhat.com> (raw)
This series enables virtio tests on SPAPR by starting
machines using qtest_pc_boot() or qtest_spapr_boot() to
use the good libqos PCI framework (pc or spapr).
It adds also some byte-swapping in virtio-pci.c as
PCI is always little-endian and the endianness of
the virtio device depends on the endianness of the
guest.
This series does not enable virtio PCI MSI-X tests on
SPAPR as this needs more work and will be the aim
of another series.
This series must be applied on top of my previous
series: "tests: enable ohci/uhci/xhci tests on PPC64"
v3:
- remove "ppc" from allowed archs for virtio-blk-test
- remove g_assert_nonnull() after g_malloc()
- add a patch to fix "vs" memory leak in virtio-scsi-test
- add a patch to remove g_assert() after qtest_spapr_boot()
and update comment qtest_vboot() to explain it never
returns NULL.
v2:
- update comments (virtio-1.0, log)
- move g_assert_nonnull() to qtest_boot()
- exit gracefully if the architecture is not supported
- replace qtest_pc_shutdown() by qtest_shutdown()
- move qvirtio_scsi_stop() to qvirtio_scsi_pci_free()
Laurent Vivier (5):
tests: fix memory leak in virtio-scsi-test
tests: don't check if qtest_spapr_boot() returns NULL
tests: use qtest_pc_boot()/qtest_shutdown() in virtio tests
qtest: evaluate endianness of the target in qtest_init()
tests: enable virtio tests on SPAPR
tests/Makefile.include | 3 +-
tests/libqos/libqos.c | 1 +
tests/libqos/virtio-pci.c | 28 +++++++-
tests/libqtest.c | 96 +++++++++++++------------
tests/libqtest.h | 16 ++++-
tests/rtas-test.c | 1 -
tests/virtio-9p-test.c | 59 ++++++++--------
tests/virtio-blk-test.c | 175 ++++++++++++++++++++++------------------------
tests/virtio-net-test.c | 57 ++++++++-------
tests/virtio-rng-test.c | 7 +-
tests/virtio-scsi-test.c | 78 +++++++++++----------
11 files changed, 283 insertions(+), 238 deletions(-)
--
2.7.4
next reply other threads:[~2016-10-01 18:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 18:55 Laurent Vivier [this message]
2016-10-01 18:56 ` [Qemu-devel] [PATCH v3 1/5] tests: fix memory leak in virtio-scsi-test Laurent Vivier
2016-10-02 8:30 ` Greg Kurz
2016-10-01 18:56 ` [Qemu-devel] [PATCH v3 2/5] tests: don't check if qtest_spapr_boot() returns NULL Laurent Vivier
2016-10-02 8:32 ` Greg Kurz
2016-10-01 18:56 ` [Qemu-devel] [PATCH v3 3/5] tests: use qtest_pc_boot()/qtest_shutdown() in virtio tests Laurent Vivier
2016-10-07 16:38 ` Greg Kurz
2016-10-07 17:54 ` Laurent Vivier
2016-10-14 8:11 ` Greg Kurz
2016-10-14 8:34 ` Laurent Vivier
2016-10-01 18:56 ` [Qemu-devel] [PATCH v3 4/5] qtest: evaluate endianness of the target in qtest_init() Laurent Vivier
2016-10-01 18:56 ` [Qemu-devel] [PATCH v3 5/5] tests: enable virtio tests on SPAPR Laurent Vivier
2016-10-02 8:36 ` Greg Kurz
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=1475348164-8593-1-git-send-email-lvivier@redhat.com \
--to=lvivier@redhat.com \
--cc=dgibson@redhat.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.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).