From: Cornelia Huck <cohuck@redhat.com>
To: Pierre Morel <pmorel@linux.ibm.com>
Cc: kvm@vger.kernel.org, frankja@linux.ibm.com, david@redhat.com,
thuth@redhat.com, imbrenda@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH v3 13/16] s390x: css: checking for CSS extensions
Date: Tue, 6 Apr 2021 17:50:24 +0200 [thread overview]
Message-ID: <20210406175024.44fe7473.cohuck@redhat.com> (raw)
In-Reply-To: <1617694853-6881-14-git-send-email-pmorel@linux.ibm.com>
On Tue, 6 Apr 2021 09:40:50 +0200
Pierre Morel <pmorel@linux.ibm.com> wrote:
> We verify that these extensions are not install before running simple
s/not install/installed/ ?
Testing extensions that are not installed does not make that much sense
:)
> tests.
>
> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
> ---
> lib/s390x/css.h | 2 ++
> s390x/css.c | 31 +++++++++++++++++++++++++++++++
> 2 files changed, 33 insertions(+)
>
> diff --git a/lib/s390x/css.h b/lib/s390x/css.h
> index d824e34..08b2974 100644
> --- a/lib/s390x/css.h
> +++ b/lib/s390x/css.h
> @@ -338,7 +338,9 @@ struct chsc_scsc {
> uint8_t reserved[9];
> struct chsc_header res;
> uint32_t res_fmt;
> +#define CSSC_ORB_EXTENSIONS 0
> #define CSSC_EXTENDED_MEASUREMENT_BLOCK 48
> +#define CSSC_FC_EXTENSIONS 88
> uint64_t general_char[255];
> uint64_t chsc_char[254];
> };
> diff --git a/s390x/css.c b/s390x/css.c
> index 26f5da6..f8c6688 100644
> --- a/s390x/css.c
> +++ b/s390x/css.c
> @@ -229,6 +229,35 @@ static void ssch_orb_ctrl(void)
> }
> }
>
> +static void ssch_orb_extension(void)
> +{
> + if (!css_test_general_feature(CSSC_ORB_EXTENSIONS)) {
> + report_skip("ORB extensions not installed");
> + return;
> + }
> + /* Place holder for checking ORB extensions */
> + report_info("ORB extensions installed but not tested");
> +}
> +
> +static void ssch_orb_fcx(void)
> +{
> + uint32_t tmp = orb->ctrl;
> +
> + if (!css_test_general_feature(CSSC_FC_EXTENSIONS)) {
> + report_skip("Fibre-channel extensions not installed");
> + return;
> + }
> +
> + report_prefix_push("Channel-Program Type Control");
> + orb->ctrl |= ORB_CTRL_CPTC;
> + expect_pgm_int();
> + ssch(test_device_sid, orb);
> + check_pgm_int_code(PGM_INT_CODE_OPERAND);
> + report_prefix_pop();
I don't quite understand what you're testing here; shouldn't the device
accept a transport-mode orb if fcx is installed? The problem would be
if the program consists of ccws instead, so it's more a malformed block
handling test?
> +
> + orb->ctrl = tmp;
> +}
> +
> static struct tests ssh_tests[] = {
> { "privilege", ssch_privilege },
> { "orb cpa zero", ssch_orb_cpa_zero },
> @@ -238,6 +267,8 @@ static struct tests ssh_tests[] = {
> { "CCW in DMA31", ssch_ccw_dma31 },
> { "ORB MIDAW unsupported", ssch_orb_midaw },
> { "ORB reserved CTRL bits", ssch_orb_ctrl },
> + { "ORB extensions", ssch_orb_extension},
> + { "FC extensions", ssch_orb_fcx},
> { NULL, NULL }
> };
>
next prev parent reply other threads:[~2021-04-06 15:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 7:40 [kvm-unit-tests PATCH v3 00/16] s390x: Testing SSCH, CSCH and HSCH for errors Pierre Morel
2021-04-06 7:40 ` [kvm-unit-tests PATCH v3 01/16] s390x: lib: css: disabling a subchannel Pierre Morel
2021-04-06 7:40 ` [kvm-unit-tests PATCH v3 02/16] s390x: lib: css: SCSW bit definitions Pierre Morel
2021-04-06 7:40 ` [kvm-unit-tests PATCH v3 03/16] s390x: css: simplify skipping tests on no device Pierre Morel
2021-04-06 12:44 ` Cornelia Huck
2021-04-07 10:53 ` Pierre Morel
2021-04-06 7:40 ` [kvm-unit-tests PATCH v3 04/16] s390x: lib: css: separate wait for IRQ and check I/O completion Pierre Morel
2021-04-06 7:40 ` [kvm-unit-tests PATCH v3 05/16] s390x: lib: css: add SCSW ctrl expectations to " Pierre Morel
2021-04-06 7:40 ` [kvm-unit-tests PATCH v3 06/16] s390x: lib: css: checking I/O errors Pierre Morel
2021-04-06 7:40 ` [kvm-unit-tests PATCH v3 07/16] s390x: css: testing ssch errors Pierre Morel
2021-04-06 7:40 ` [kvm-unit-tests PATCH v3 08/16] s390x: css: ssch check for cpa zero Pierre Morel
2021-04-06 7:40 ` [kvm-unit-tests PATCH v3 09/16] s390x: css: ssch with mis aligned ORB Pierre Morel
2021-04-06 7:40 ` [kvm-unit-tests PATCH v3 10/16] s390x: css: ssch checking addressing errors Pierre Morel
2021-04-06 7:40 ` [kvm-unit-tests PATCH v3 11/16] s390x: css: No support for MIDAW Pierre Morel
2021-04-06 15:58 ` Cornelia Huck
2021-04-07 10:06 ` Pierre Morel
2021-04-07 10:14 ` Cornelia Huck
2021-04-06 7:40 ` [kvm-unit-tests PATCH v3 12/16] s390x: css: Check ORB reserved bits Pierre Morel
2021-04-06 15:51 ` Cornelia Huck
2021-04-07 10:07 ` Pierre Morel
2021-04-07 10:15 ` Cornelia Huck
2021-04-06 7:40 ` [kvm-unit-tests PATCH v3 13/16] s390x: css: checking for CSS extensions Pierre Morel
2021-04-06 15:50 ` Cornelia Huck [this message]
2021-04-07 10:42 ` Pierre Morel
2021-04-06 7:40 ` [kvm-unit-tests PATCH v3 14/16] s390x: css: issuing SSCH when the channel is status pending Pierre Morel
2021-04-06 15:34 ` Cornelia Huck
2021-04-07 10:46 ` Pierre Morel
2021-04-06 7:40 ` [kvm-unit-tests PATCH v3 15/16] s390x: css: testing halt subchannel Pierre Morel
2021-04-06 7:40 ` [kvm-unit-tests PATCH v3 16/16] s390x: css: testing clear subchannel Pierre Morel
2021-04-06 12:21 ` [kvm-unit-tests PATCH v3 00/16] s390x: Testing SSCH, CSCH and HSCH for errors 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=20210406175024.44fe7473.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@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