From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
haoqf@linux.vnet.ibm.com, qemu-block@nongnu.org,
david@redhat.com, agraf@suse.de, qemu-devel@nongnu.org,
borntraeger@de.ibm.com, mreitz@redhat.com,
"Lukáš Doktor" <ldoktor@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/3] iotests: use -ccw on s390x for 051
Date: Tue, 12 Sep 2017 18:05:27 +0200 [thread overview]
Message-ID: <20170912180527.1f0e80b5.cohuck@redhat.com> (raw)
In-Reply-To: <4374d570-cee8-5f82-7187-dcb7bf57bf55@redhat.com>
On Fri, 8 Sep 2017 17:55:29 +0200
Thomas Huth <thuth@redhat.com> wrote:
> On 08.09.2017 13:54, Kevin Wolf wrote:
> > Am 08.09.2017 um 13:24 hat Cornelia Huck geschrieben:
> >> On Fri, 8 Sep 2017 13:04:25 +0200
> >> Kevin Wolf <kwolf@redhat.com> wrote:
> >>
> >>> 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.
> >>
> >> Are there no non-pc and non-s390 machines for which this is run?
> >
> > Who knows? But I'm not aware of anyone who is interested in something
> > else and has contributed to the test cases until now.
>
> FWIW, as far as I know, Lukáš is running this test also on ppc64 in our
> weekly regression run. So it would be good to keep that working, please :-)
>
> >> Another approach would be to drop the -pci postfix, but I don't want to
> >> introduce more usage of aliases.
> >
> > Maybe that would indeed be the easiest way. As long as we don't intend
> > to remove the alias from qemu, there's no reason not to use it in tests.
>
> Maybe we should even use it in a couple of places on purpose - so we get
> some test coverage for them?
FWIW, using the the sed post-run filtering works well for 051, but it
is driving me bonkers on 067 (or maybe I should just call it a day...)
We could use the sed approach for 051 and the alias approach on 067 -
that way we would also test aliases :)
Any preferences by the iotest maintainers?
[I'd be happy if iotests worked again on s390x...]
next prev parent reply other threads:[~2017-09-12 16: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
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 [this message]
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=20170912180527.1f0e80b5.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=haoqf@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=ldoktor@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).