From: Cornelia Huck <cohuck@redhat.com>
To: Pierre Morel <pmorel@linux.ibm.com>
Cc: Thomas Huth <thuth@redhat.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
frankja@linux.ibm.com, david@redhat.com
Subject: Re: [kvm-unit-tests PATCH v8 10/12] s390x: css: stsch, enumeration test
Date: Wed, 10 Jun 2020 17:54:29 +0200 [thread overview]
Message-ID: <20200610175429.401a58ea.cohuck@redhat.com> (raw)
In-Reply-To: <a9a44f1d-2179-5d95-f45f-172000f7a3c1@linux.ibm.com>
On Tue, 9 Jun 2020 14:20:35 +0200
Pierre Morel <pmorel@linux.ibm.com> wrote:
> On 2020-06-09 09:39, Thomas Huth wrote:
> > On 08/06/2020 10.12, Pierre Morel wrote:
> >> +static void test_enumerate(void)
> >> +{
> >> + test_device_sid = css_enumerate();
> >> + if (test_device_sid & SCHID_ONE) {
> >> + report(1, "First device schid: 0x%08x", test_device_sid);
> >> + return;
> >> + }
> >> +
> >> + switch (test_device_sid) {
> >> + case 0:
> >> + report (0, "No I/O device found");
> >> + break;
> >> + default: /* 1 or 2 should never happened for STSCH */
> >> + report(0, "Unexpected cc=%d during enumeration",
> >> + test_device_sid);
> >> + return;
> >> + }
> >
> > Ok, so here is now the test failure for the cc=1 or 2 that should never
> > happen. That means currently you print out the CC for this error twice.
> > One time should be enough, either here, or use an report_abort() in the
> > css_enumerate(), I'd say.
> >
> > Anyway, can you please replace this switch statement with a "if
> > (!test_device_sid)" instead? Or do you plan to add more "case"
> > statements later?
>
> I will use the repor_abort() in the css_enumerate() so there
> is only two case, I find a channel or not, so I don't even need the
> second if :) .
Yeah, testing only for SCHID_ONE present or not makes this a lot less
confusing.
next prev parent reply other threads:[~2020-06-10 15:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 8:12 [kvm-unit-tests PATCH v8 00/12] s390x: Testing the Channel Subsystem I/O Pierre Morel
2020-06-08 8:12 ` [kvm-unit-tests PATCH v8 01/12] s390x: Use PSW bits definitions in cstart Pierre Morel
2020-06-08 8:43 ` Thomas Huth
2020-06-08 14:33 ` Pierre Morel
2020-06-08 14:52 ` Thomas Huth
2020-06-08 15:28 ` Pierre Morel
2020-06-08 15:30 ` Thomas Huth
2020-06-08 8:12 ` [kvm-unit-tests PATCH v8 02/12] s390x: Move control register bit definitions and add AFP to them Pierre Morel
2020-06-08 8:45 ` Thomas Huth
2020-06-08 14:25 ` Pierre Morel
2020-06-08 8:12 ` [kvm-unit-tests PATCH v8 03/12] s390x: saving regs for interrupts Pierre Morel
2020-06-08 9:05 ` Thomas Huth
2020-06-08 14:24 ` Pierre Morel
2020-06-08 15:29 ` Thomas Huth
2020-06-08 16:03 ` Pierre Morel
2020-06-08 8:12 ` [kvm-unit-tests PATCH v8 04/12] s390x: interrupt registration Pierre Morel
2020-06-08 8:12 ` [kvm-unit-tests PATCH v8 05/12] s390x: export the clock get_clock_ms() utility Pierre Morel
2020-06-08 8:12 ` [kvm-unit-tests PATCH v8 06/12] s390x: clock and delays caluculations Pierre Morel
2020-06-08 15:55 ` Thomas Huth
2020-06-08 16:16 ` Pierre Morel
2020-06-08 8:12 ` [kvm-unit-tests PATCH v8 07/12] s390x: define function to wait for interrupt Pierre Morel
2020-06-09 5:07 ` Thomas Huth
2020-06-09 7:54 ` Pierre Morel
2020-06-08 8:12 ` [kvm-unit-tests PATCH v8 08/12] s390x: retrieve decimal and hexadecimal kernel parameters Pierre Morel
2020-06-09 5:21 ` Thomas Huth
2020-06-09 7:53 ` Pierre Morel
2020-06-08 8:12 ` [kvm-unit-tests PATCH v8 09/12] s390x: Library resources for CSS tests Pierre Morel
2020-06-09 7:09 ` Thomas Huth
2020-06-09 15:01 ` Pierre Morel
2020-06-10 14:51 ` Thomas Huth
2020-06-10 15:10 ` Pierre Morel
2020-06-08 8:12 ` [kvm-unit-tests PATCH v8 10/12] s390x: css: stsch, enumeration test Pierre Morel
2020-06-09 7:39 ` Thomas Huth
2020-06-09 12:20 ` Pierre Morel
2020-06-10 15:54 ` Cornelia Huck [this message]
2020-06-08 8:13 ` [kvm-unit-tests PATCH v8 11/12] s390x: css: msch, enable test Pierre Morel
2020-06-09 7:47 ` Thomas Huth
2020-06-09 7:56 ` Pierre Morel
2020-06-08 8:13 ` [kvm-unit-tests PATCH v8 12/12] s390x: css: ssch/tsch with sense and interrupt Pierre Morel
2020-06-09 8:15 ` Thomas Huth
2020-06-09 12:02 ` Pierre Morel
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=20200610175429.401a58ea.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pmorel@linux.ibm.com \
--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