From: David Hildenbrand <david@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>, kwolf@redhat.com, mreitz@redhat.com
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
borntraeger@de.ibm.com, agraf@suse.de, thuth@redhat.com,
haoqf@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v2 3/3] iotests: use virtio aliases for 067
Date: Wed, 13 Sep 2017 14:02:10 +0200 [thread overview]
Message-ID: <d1cbe726-0109-4b3d-a1f7-64fadbbd54c1@redhat.com> (raw)
In-Reply-To: <20170913091038.2900-4-cohuck@redhat.com>
On 13.09.2017 11:10, Cornelia Huck wrote:
> The default cpu model on s390x does not provide zPCI, which is
> not yet wired up on tcg. Moreover, virtio-ccw is the standard
> on s390x.
>
> Using virtio-scsi will implicitly pick the right device, so just
> switch to that for simplicity.
>
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
> tests/qemu-iotests/067 | 3 ++-
> tests/qemu-iotests/067.out | 2 +-
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/tests/qemu-iotests/067 b/tests/qemu-iotests/067
> index 5d4ca4bc61..cbb3da286a 100755
> --- a/tests/qemu-iotests/067
> +++ b/tests/qemu-iotests/067
> @@ -141,7 +141,7 @@ echo
> echo === Empty drive with -device and device_del ===
> echo
>
> -run_qemu -device virtio-scsi-pci -device scsi-cd,id=cd0 <<EOF
> +run_qemu -device virtio-scsi -device scsi-cd,id=cd0 <<EOF
> { "execute": "qmp_capabilities" }
> { "execute": "query-block" }
> { "execute": "device_del", "arguments": { "id": "cd0" } }
> @@ -150,6 +150,7 @@ run_qemu -device virtio-scsi-pci -device scsi-cd,id=cd0 <<EOF
> { "execute": "quit" }
> EOF
>
> +
> # success, all done
> echo "*** done"
> rm -f $seq.full
> diff --git a/tests/qemu-iotests/067.out b/tests/qemu-iotests/067.out
> index bd70557ddc..58e83c4505 100644
> --- a/tests/qemu-iotests/067.out
> +++ b/tests/qemu-iotests/067.out
> @@ -419,7 +419,7 @@ Testing:
>
> === Empty drive with -device and device_del ===
>
> -Testing: -device virtio-scsi-pci -device scsi-cd,id=cd0
> +Testing: -device virtio-scsi -device scsi-cd,id=cd0
> {
> QMP_VERSION
> }
>
Certainly not wrong to use the old alias in some tests, as long as we
test both variants.
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David
next prev parent reply other threads:[~2017-09-13 12:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 9:10 [Qemu-devel] [PATCH v2 0/3] iotests: cure s390x failures by switching to ccw/aliases Cornelia Huck
2017-09-13 9:10 ` [Qemu-devel] [PATCH v2 1/3] iotests: use -ccw on s390x for 040, 139, and 182 Cornelia Huck
2017-09-13 11:59 ` David Hildenbrand
2017-09-13 9:10 ` [Qemu-devel] [PATCH v2 2/3] iotests: use -ccw on s390x for 051 Cornelia Huck
2017-09-13 9:18 ` Thomas Huth
2017-09-13 11:57 ` David Hildenbrand
2017-09-13 9:10 ` [Qemu-devel] [PATCH v2 3/3] iotests: use virtio aliases for 067 Cornelia Huck
2017-09-13 9:17 ` Thomas Huth
2017-09-13 12:02 ` David Hildenbrand [this message]
2017-09-15 7:04 ` [Qemu-devel] [PATCH v2 0/3] iotests: cure s390x failures by switching to ccw/aliases QingFeng Hao
2017-09-15 12:11 ` 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=d1cbe726-0109-4b3d-a1f7-64fadbbd54c1@redhat.com \
--to=david@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=haoqf@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@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).