From: Bo Tu <tubo@linux.vnet.ibm.com>
To: Max Reitz <mreitz@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, silbe@linux.vnet.ibm.com, armbru@redhat.com,
mimu@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v4 2/3] qemu-iotests: s390x: fix test 051
Date: Sat, 5 Dec 2015 06:20:46 +0800 [thread overview]
Message-ID: <566211BE.4080104@linux.vnet.ibm.com> (raw)
In-Reply-To: <566203DD.9080005@redhat.com>
Hi Max:
在 2015/12/5 5:21, Max Reitz 写道:
> On 03.12.2015 11:01, Bo Tu wrote:
>> From: Bo Tu <tubo@linux.vnet.ibm.com>
>>
>> The tests for ide device should only be tested for the pc
>> platform.
>> Set device_id to "drive0", and replace every "-drive file..."
>> by "-drive file=...,if=none,id=$device_id", then x86 and s390x
>> can get the common output in the test of "Snapshot mode".
>> Warning message expected for s390x when drive without device.
>> A x86 platform specific output file is also needed.
>>
>> Reviewed-by: Sascha Silbe <silbe@linux.vnet.ibm.com>
>> Signed-off-by: Bo Tu <tubo@linux.vnet.ibm.com>
>> ---
>> tests/qemu-iotests/051 | 95 ++++++----
>> tests/qemu-iotests/051.out | 163 ++++------------
>> tests/qemu-iotests/051.pc.out | 422 ++++++++++++++++++++++++++++++++++++++++++
>> 3 files changed, 521 insertions(+), 159 deletions(-)
>> create mode 100644 tests/qemu-iotests/051.pc.out
>
> I like the overall design now, but I think we can do more still.
>
> As evidenced by changes in the reference output from "ide0-hd0" to
> "virtio0", there are still more places which are missing an explicit if
> (like if=none) and id in 051 and are thus currently subject to whatever
> the target platform uses as the default (which happens to be
> virtio/virtio0 for s390). I think all of the places in 051 which do not
> specify an interface and ID should do so (i.e. if=none,id=drive0).
>
> Next, there are the warnings regarding orphaned drives. I'm only just
> now asking myself the question where they really come from, and I guess
> it's mostly the fact that we are trying to use if=ide, if=floppy and
> if=scsi which do not seem to be supported by s390. I guess we should
> simply not do any of the tests which use any of these interfaces (or,
> phrased differently, only do tests which use if=none or if=virtio).
>
> I'd be willing to merge this patch now anyway, though, as long as there
> will be a follow-up patch addressing these issues, if you agree.
I will create a follow-up patch to address these issues you mentioned.
thanks a lot for your review!! Have a good weekend.
>
> Max
>
next prev parent reply other threads:[~2015-12-04 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 10:01 [Qemu-devel] [PATCH v4 0/3] Update tests/qemu-iotests failing cases for the s390 platform Bo Tu
2015-12-03 10:01 ` [Qemu-devel] [PATCH v4 1/3] qemu-iotests: refine common.config Bo Tu
2015-12-03 10:01 ` [Qemu-devel] [PATCH v4 2/3] qemu-iotests: s390x: fix test 051 Bo Tu
2015-12-04 21:21 ` Max Reitz
2015-12-04 22:20 ` Bo Tu [this message]
2015-12-03 10:01 ` [Qemu-devel] [PATCH v4 3/3] qemu-iotests: s390x: fix test 068 Bo Tu
2015-12-04 21:34 ` [Qemu-devel] [PATCH v4 0/3] Update tests/qemu-iotests failing cases for the s390 platform Max Reitz
2015-12-04 23:32 ` Max Reitz
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=566211BE.4080104@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).