From: tu bo <tubo@linux.vnet.ibm.com>
To: Max Reitz <mreitz@redhat.com>,
Sascha Silbe <silbe@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Cc: kwolf@redhat.com, armbru@redhat.com, mimu@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v2 2/4] qemu-iotests: s390x: fix test 051
Date: Thu, 26 Nov 2015 18:15:17 +0800 [thread overview]
Message-ID: <5656DBB5.7060207@linux.vnet.ibm.com> (raw)
In-Reply-To: <5655D6C7.5050903@redhat.com>
Hi Max:
On 11/25/2015 11:41 PM, Max Reitz wrote:
> On 24.11.2015 22:17, Sascha Silbe wrote:
>> This PC/s390x-only hunk looks like an oversight to me.
>
> Not really, see
> http://lists.nongnu.org/archive/html/qemu-devel/2015-02/msg01906.html
> and
> http://lists.nongnu.org/archive/html/qemu-devel/2015-04/msg02851.html
>
> I noticed, but I am fine with it since the tests probably won't run on
> anything but x86/pc and s390 anyway (without modifications; most of the
> changes this series is making to make the iotests work on s390 are
> necessary for other non-pc platforms as well, and that shows to me that
> apparently nobody tried to run the iotests on non-pc platforms before
> s390, or didn't care enough about them to fix them).
>
>> We should make
>> one of the options the default. I'd prefer defaulting to virtio (see
>> below), but since the test previously hard-coded IDE that would be fine,
>> too.
>
> In my first reply above, I noted that virtio0 may not be available on
> all platforms either. Therefore, I'd rather have an explicit list of
> platforms there than an asterisk where it does not belong.
>
> However, my second reply above spawned a bit of a discussion, where
> Kevin simply proposed to change the ID of the drive to something known,
> i.e. just set the ID by adding an id=drive0 or something to the -drive
> parameter.
>
> Thanks for reminding me of the above, I had already forgotten. Indeed,
> we should just add id=drive0 to the -drive parameter and use drive0. A
> similar solution may be possible in most other places as well where PC
> and s390 differ due to the names of the default devices available.
thanks for the reminder :-)
Yes, Kevin mentioned that we can use "id=testdisk" because it's the same
on all platforms. Please refer this link:
http://lists.nongnu.org/archive/html/qemu-devel/2015-04/msg03715.html
For test 130, I used "qemu -drive id=testdisk" for both pc and s390x.
For test 051, I didn't find a way to do the same thing for qemu-io.
next prev parent reply other threads:[~2015-11-26 10:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 2:26 [Qemu-devel] [PATCH v2 0/4] Update tests/qemu-iotests failing cases for the s390 platform Bo Tu
2015-11-04 2:26 ` [Qemu-devel] [PATCH v2 1/4] qemu-iotests: refine common.config Bo Tu
2015-11-18 16:45 ` Max Reitz
2015-11-19 5:58 ` tu bo
2015-11-04 2:26 ` [Qemu-devel] [PATCH v2 2/4] qemu-iotests: s390x: fix test 051 Bo Tu
2015-11-18 16:52 ` Max Reitz
2015-11-19 7:28 ` tu bo
2015-11-20 16:24 ` Max Reitz
2015-11-23 3:34 ` tu bo
2015-11-24 21:17 ` Sascha Silbe
2015-11-25 15:41 ` Max Reitz
2015-11-26 10:15 ` tu bo [this message]
2015-11-04 2:26 ` [Qemu-devel] [PATCH v2 3/4] qemu-iotests: s390x: fix test 068 Bo Tu
2015-11-18 16:57 ` Max Reitz
2015-11-04 2:26 ` [Qemu-devel] [PATCH v2 4/4] qemu-iotests: disable VNC server for test 120 Bo Tu
2015-11-18 16:56 ` Max Reitz
2015-11-19 7:06 ` tu bo
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=5656DBB5.7060207@linux.vnet.ibm.com \
--to=tubo@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mimu@linux.vnet.ibm.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=silbe@linux.vnet.ibm.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).