qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: tu bo <tubo@linux.vnet.ibm.com>
To: Max Reitz <mreitz@redhat.com>,
	qemu-devel@nongnu.org, silbe@linux.vnet.ibm.com
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: Mon, 23 Nov 2015 11:34:44 +0800	[thread overview]
Message-ID: <56528954.50102@linux.vnet.ibm.com> (raw)
In-Reply-To: <564F493C.3030501@redhat.com>

Hi Max, Sascha:

On 11/21/2015 12:24 AM, Max Reitz wrote:
> On 19.11.2015 08:28, tu bo wrote:
>> Hi Max:
>>
>> On 11/19/2015 12:52 AM, Max Reitz wrote:
>>> On 04.11.2015 03:26, Bo Tu wrote:
>>>> The tests for device type "ide_cd" should only be tested for the pc
>>>> platform.
>>>> The default device id of hard disk on the s390 platform differs to that
>>>> of the x86 platform. A new variable device_id is defined and "virtio0"
>>>> set for the s390 platform. A x86 platform specific output file is also
>>>> needed.
>>>> Warning message expected for s390x when drive without device.
>>>>
>>>> Reviewed-by: Sascha Silbe <silbe@linux.vnet.ibm.com>
>>>> Signed-off-by: Bo Tu <tubo@linux.vnet.ibm.com>
>>>> ---
>>>>    tests/qemu-iotests/051        |  99 ++++++----
>>>>    tests/qemu-iotests/051.out    | 143 +++-----------
>>>>    tests/qemu-iotests/051.pc.out | 422
>>>> ++++++++++++++++++++++++++++++++++++++++++
>>>>    3 files changed, 515 insertions(+), 149 deletions(-)
>>>>    create mode 100644 tests/qemu-iotests/051.pc.out
>>>>
>>>
>>> [...]
>>>
>>>> diff --git a/tests/qemu-iotests/051.out b/tests/qemu-iotests/051.out
>>>> index 7765aa0..d17c969 100644
>>>> --- a/tests/qemu-iotests/051.out
>>>> +++ b/tests/qemu-iotests/051.out
>>>
>>> [...]
>>>
>>>> @@ -109,20 +109,23 @@ QEMU X.Y.Z monitor - type 'help' for more
>>>> information
>>>>
>>>>    Testing: -drive if=floppy
>>>>    QEMU X.Y.Z monitor - type 'help' for more information
>>>> -(qemu) q^[[K^[[Dqu^[[K^[[D^[[Dqui^[[K^[[D^[[D^[[Dquit^[[K
>>>> +(qemu) Warning: Orphaned drive without device:
>>>> id=floppy0,file=,if=floppy,bus=0,unit=0
>>>> +q^[[K^[[Dqu^[[K^[[D^[[Dqui^[[K^[[D^[[D^[[Dquit^[[K
>>>
>>> I'd still like these warnings to be filtered out (as I wrote in my reply
>>> to the original RFC's v4, and as was done in later versions of that RFC
>>> (the _filter_orphan function e.g. in
>>> http://lists.nongnu.org/archive/html/qemu-devel/2015-05/msg04816.html).
>>>
>>
>> I did more investigation about this.
>> "Warning: Orphaned drive without device:.*"  is expected for s390x, when
>> we define a drive without device, also this drive is not default
>> and interface is not "none".  Please refer line 228,229 in blockdev.c:
>>      218 bool drive_check_orphaned(void)
>>      219 {
>>      220     BlockBackend *blk;
>>      221     DriveInfo *dinfo;
>>      222     bool rs = false;
>>      223
>>      224     for (blk = blk_next(NULL); blk; blk = blk_next(blk)) {
>>      225         dinfo = blk_legacy_dinfo(blk);
>>      226         /* If dinfo->bdrv->dev is NULL, it has no device
>> attached. */
>>      227         /* Unless this is a default drive, this may be an
>> oversight. */
>>      228         if (!blk_get_attached_dev(blk) && !dinfo->is_default &&
>>      229             dinfo->type != IF_NONE) {
>>      230             fprintf(stderr, "Warning: Orphaned drive without
>> device: "
>>      231                     "id=%s,file=%s,if=%s,bus=%d,unit=%d\n",
>>      232                     blk_name(blk), blk_bs(blk)->filename,
>> if_name[dinfo->type],
>>      233                     dinfo->bus, dinfo->unit);
>>      234             rs = true;
>>      235         }
>>      236     }
>>
>> For example,  "run_qemu -drive if=scsi"  will generate orphan warning
>> message for s390x,  but "run_qemu -drive if=virtio"  will not generate
>> orphan warning message,  since virtio is a default drive.
>>
>> so I removed  _filter_orphan() in common.filter,  and added orphan
>> warning message(ie: for the output of "run_qemu -drive if=scsi") in
>> output file for s390x.   thanks
>
> OK, so it is expected for s390x; however, this is strictly speaking not
> the output file for s390x but for any platform but PC. That's why I'd
> rather not have it in this “generic” reference output.
>
> This patch already assumes that the iotests only support s390 and PC
> (hunk @@ -251,28 +273,37 @@ in 051 adds a case statement which knows
> only these two cases). Therefore, I would be fine with renaming this
> reference output file to "051.s390.out" with a copy
> "051.s390-ccw-virtio.out" and just removing the generic "051.out". Then
> you can keep the warnings in.
>

It looks good to me. thanks

Hi Sascha:
This change is to rename 051.out to "051.s390.out" with a copy
"051.s390-ccw-virtio.out" and just to remove the generic "051.out". Is 
this fine to you?  thanks

> (Or you filter the warnings out and keep it as "051.out".)
>
> Max
>

  reply	other threads:[~2015-11-23  3:34 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 [this message]
2015-11-24 21:17         ` Sascha Silbe
2015-11-25 15:41           ` Max Reitz
2015-11-26 10:15             ` tu bo
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=56528954.50102@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).