qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: QingFeng Hao <haoqf@linux.vnet.ibm.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,
	david@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/3] iotests: cure s390x failures by switching to ccw/aliases
Date: Fri, 15 Sep 2017 15:04:56 +0800	[thread overview]
Message-ID: <d72eb721-18de-af12-0ac7-62889a3f7b24@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170913091038.2900-1-cohuck@redhat.com>

Reviewed-by: QingFeng Hao <haoqf@linux.vnet.ibm.com>

for the series of patches.

Thanks


在 2017/9/13 17:10, Cornelia Huck 写道:
> Recent changes in s390x made pci support dependant on the zpci cpu
> feature, which is not provided on all models (and not on by default).
> This means we cannot instatiate pci devices on a standard qemu
> invocation for s390x. Moreover, the zpci instructions are not even
> wired up for tcg yet, so actually doing anything with those pci devices
> is bound to fail on tcg.
>
> For 040, 051, 139, and 182, this can be fixed by switching to virtio-ccw
> from virtio-pci on s390x. 051 also needs a bit of post-processing on
> the output.
>
> For 067, it is easier to switch to virtio aliases, which will pick
> virtio-ccw on s390x and virtio-pci elsewhere. It also exercises the
> aliasing path.
>
> v1->v2:
> - avoid adding new reference output by adding post-processing to 051
>    and switching to aliases for 067
>
> Cornelia Huck (3):
>    iotests: use -ccw on s390x for 040, 139, and 182
>    iotests: use -ccw on s390x for 051
>    iotests: use virtio aliases for 067
>
>   tests/qemu-iotests/040        |  6 +++++-
>   tests/qemu-iotests/051        | 12 +++++++++++-
>   tests/qemu-iotests/051.out    |  2 +-
>   tests/qemu-iotests/051.pc.out |  2 +-
>   tests/qemu-iotests/067        |  3 ++-
>   tests/qemu-iotests/067.out    |  2 +-
>   tests/qemu-iotests/139        | 12 ++++++++++--
>   tests/qemu-iotests/182        | 13 +++++++++++--
>   8 files changed, 42 insertions(+), 10 deletions(-)
>

-- 
Regards
QingFeng Hao

  parent reply	other threads:[~2017-09-15  7:05 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
2017-09-15  7:04 ` QingFeng Hao [this message]
2017-09-15 12:11 ` [Qemu-devel] [PATCH v2 0/3] iotests: cure s390x failures by switching to ccw/aliases 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=d72eb721-18de-af12-0ac7-62889a3f7b24@linux.vnet.ibm.com \
    --to=haoqf@linux.vnet.ibm.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.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).