qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: mreitz@redhat.com, qemu-block@nongnu.org, qemu-devel@nongnu.org,
	borntraeger@de.ibm.com, agraf@suse.de, thuth@redhat.com,
	david@redhat.com, haoqf@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 2/3] iotests: use -ccw on s390x for 051
Date: Fri, 8 Sep 2017 13:04:25 +0200	[thread overview]
Message-ID: <20170908110425.GC3283@localhost.localdomain> (raw)
In-Reply-To: <20170905151614.31303-3-cohuck@redhat.com>

Am 05.09.2017 um 17:16 hat Cornelia Huck geschrieben:
> 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, so use the -ccw instead of the -pci versions of virtio
> devices on s390x.
> 
> Provide an output file for s390x.
> 
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
>  tests/qemu-iotests/051                     |   9 +-
>  tests/qemu-iotests/051.s390-ccw-virtio.out | 434 +++++++++++++++++++++++++++++
>  2 files changed, 442 insertions(+), 1 deletion(-)
>  create mode 100644 tests/qemu-iotests/051.s390-ccw-virtio.out

It's already a pain to have two separate output files for 051, let's try
to avoid adding a third one. Even more so since I think that the split
between 051.out and 051.pc.out was already made for s390, so I'm not
sure if anyone would actually still make use of the plain 051.out
output if s390 got it's own one.

> diff --git a/tests/qemu-iotests/051 b/tests/qemu-iotests/051
> index c8cfc764bc..f6ad0f4f0b 100755
> --- a/tests/qemu-iotests/051
> +++ b/tests/qemu-iotests/051
> @@ -103,7 +103,14 @@ echo
>  echo === Device without drive ===
>  echo
>  
> -run_qemu -device virtio-scsi-pci -device scsi-hd
> +case "$QEMU_DEFAULT_MACHINE" in
> +  s390-ccw-virtio)
> +      run_qemu -device virtio-scsi-ccw -device scsi-hd
> +      ;;
> +  *)
> +      run_qemu -device virtio-scsi-pci -device scsi-hd
> +      ;;
> +esac

The only real difference between 051.out and 051.s390-ccw-virtio.out is
in this one command line. So if we don't want to just skip this part of
the test for non-pc like we already skip ther parts, we generally solve
this kind of thing by just filtering out strings that differ between
setups.

For example:

    case "$QEMU_DEFAULT_MACHINE" in
      s390-ccw-virtio)
          virtio_scsi=virtio-scsi-ccw
          ;;
      *)
          virtio_scsi=virtio-scsi-pci
          ;;
    esac

    run_qemu -device $virtio_scsi -device scsi-hd |
        sed -e "s/$virtio_scsi/VIRTIO-SCSI/"

Kevin

  parent reply	other threads:[~2017-09-08 11:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05 15:16 [Qemu-devel] [PATCH 0/3] iotests: cure s390x failures by switching to ccw Cornelia Huck
2017-09-05 15:16 ` [Qemu-devel] [PATCH 1/3] iotests: use -ccw on s390x for 040, 139, and 182 Cornelia Huck
2017-09-08 11:07   ` Kevin Wolf
2017-09-05 15:16 ` [Qemu-devel] [PATCH 2/3] iotests: use -ccw on s390x for 051 Cornelia Huck
2017-09-06  7:19   ` QingFeng Hao
2017-09-06  7:32     ` Cornelia Huck
2017-09-06  8:42       ` QingFeng Hao
2017-09-08 11:04   ` Kevin Wolf [this message]
2017-09-08 11:24     ` Cornelia Huck
2017-09-08 11:54       ` Kevin Wolf
2017-09-08 15:55         ` Thomas Huth
2017-09-11 10:29           ` Lukáš Doktor
2017-09-12 16:05           ` Cornelia Huck
2017-09-12 16:16             ` Kevin Wolf
2017-09-05 15:16 ` [Qemu-devel] [PATCH 3/3] iotests: use -ccw on s390x for 067 Cornelia Huck
2017-09-08 11:06   ` Kevin Wolf
2017-09-06  6:57 ` [Qemu-devel] [PATCH 0/3] iotests: cure s390x failures by switching to ccw QingFeng Hao
2017-09-06  7:17   ` Cornelia Huck
2017-09-06  7:59   ` Cornelia Huck
2017-09-06  8:09     ` Yi Min Zhao

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=20170908110425.GC3283@localhost.localdomain \
    --to=kwolf@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=haoqf@linux.vnet.ibm.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).