From: Pierre Morel <pmorel@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, frankja@linux.ibm.com,
david@redhat.com, cohuck@redhat.com
Subject: Re: [kvm-unit-tests PATCH v8 11/12] s390x: css: msch, enable test
Date: Tue, 9 Jun 2020 09:56:03 +0200 [thread overview]
Message-ID: <142b419e-3136-750d-17c4-db17724aa5ee@linux.ibm.com> (raw)
In-Reply-To: <f888f043-6177-5bcc-f84f-437015457cf3@redhat.com>
On 2020-06-09 09:47, Thomas Huth wrote:
> On 08/06/2020 10.13, Pierre Morel wrote:
>> A second step when testing the channel subsystem is to prepare a channel
>> for use.
>> This includes:
>> - Get the current subchannel Information Block (SCHIB) using STSCH
>> - Update it in memory to set the ENABLE bit
>> - Tell the CSS that the SCHIB has been modified using MSCH
>> - Get the SCHIB from the CSS again to verify that the subchannel is
>> enabled.
>> - If the command succeeds but subchannel is not enabled retry a
>> predefined retries count.
>> - If the command fails, report the failure and do not retry, even
>> if cc indicates a busy/status pending as we do not expect this.
>>
>> This tests the MSCH instruction to enable a channel succesfuly.
>> This some retries are done and in case of error, and if the retries
>> count is exceeded, a report is made.
>>
>> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
>> ---
>> lib/s390x/css_lib.c | 60 +++++++++++++++++++++++++++++++++++++++++++++
>> s390x/css.c | 18 ++++++++++++++
>> 2 files changed, 78 insertions(+)
>>
>> diff --git a/lib/s390x/css_lib.c b/lib/s390x/css_lib.c
>> index dc5a512..831a116 100644
>> --- a/lib/s390x/css_lib.c
>> +++ b/lib/s390x/css_lib.c
>> @@ -15,6 +15,7 @@
>> #include <string.h>
>> #include <interrupt.h>
>> #include <asm/arch_def.h>
>> +#include <asm/time.h>
>>
>> #include <css.h>
>>
>> @@ -68,3 +69,62 @@ out:
>> scn, scn_found, dev_found);
>> return schid;
>> }
>> +
>> +int css_enable(int schid)
>> +{
>> + struct pmcw *pmcw = &schib.pmcw;
>> + int retry_count = 0;
>> + int cc;
>> +
>> + /* Read the SCHIB for this subchannel */
>> + cc = stsch(schid, &schib);
>> + if (cc) {
>> + report_info("stsch failed with cc=%d", cc);
>> + return cc;
>> + }
>> +
>> + if (pmcw->flags & PMCW_ENABLE) {
>> + report_info("stsch: sch %08x already enabled", schid);
>> + return 0;
>> + }
>> +
>> +retry:
>> + /* Update the SCHIB to enable the channel */
>> + pmcw->flags |= PMCW_ENABLE;
>> +
>> + /* Tell the CSS we want to modify the subchannel */
>> + cc = msch(schid, &schib);
>> + if (cc) {
>> + /*
>> + * If the subchannel is status pending or
>> + * if a function is in progress,
>> + * we consider both cases as errors.
>> + */
>> + report_info("msch failed with cc=%d", cc);
>> + return cc;
>> + }
>> +
>> + /*
>> + * Read the SCHIB again to verify the enablement
>> + */
>> + cc = stsch(schid, &schib);
>> + if (cc) {
>> + report_info("stsch failed with cc=%d", cc);
>> + return cc;
>> + }
>> +
>> + if (pmcw->flags & PMCW_ENABLE) {
>> + report_info("Subchannel %08x enabled after %d retries",
>> + schid, retry_count);
>> + return 0;
>> + }
>> +
>> + if (retry_count++ < MAX_ENABLE_RETRIES) {
>> + mdelay(10); /* the hardware was not ready, give it some time */
>> + goto retry;
>> + }
>> +
>> + report_info("msch: enabling sch %08x failed after %d retries. pmcw flags: %x",
>> + schid, retry_count, pmcw->flags);
>> + return -1;
>> +}
>> diff --git a/s390x/css.c b/s390x/css.c
>> index f0e8f47..6f58d4a 100644
>> --- a/s390x/css.c
>> +++ b/s390x/css.c
>> @@ -40,11 +40,29 @@ static void test_enumerate(void)
>> }
>> }
>>
>> +static void test_enable(void)
>> +{
>> + int cc;
>> +
>> + if (!test_device_sid) {
>> + report_skip("No device");
>> + return;
>> + }
>> +
>> + cc = css_enable(test_device_sid);
>> +
>> + if (cc)
>> + report(0, "Failed to enable subchannel %08x", test_device_sid);
>> + else
>> + report(1, "Subchannel %08x enabled", test_device_sid);
>
> Could you please write this as:
>
> report(cc == 1, "Enable subchannel %08x", test_device_sid);
>
> ... checking for a right value is the whole point of the first parameter
> of report() :-)
>
> Thanks,
> Thomas
>
OK, thanks,
Pierre
--
Pierre Morel
IBM Lab Boeblingen
next prev parent reply other threads:[~2020-06-09 7:56 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
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 [this message]
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=142b419e-3136-750d-17c4-db17724aa5ee@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.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