From: Pierre Morel <pmorel@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.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 v1 2/6] s390x: lib: css: SCSW bit definitions
Date: Fri, 19 Mar 2021 16:30:12 +0100 [thread overview]
Message-ID: <d39a43c1-4640-1175-31d8-28d90133e63e@linux.ibm.com> (raw)
In-Reply-To: <20210319111626.20b9cd72.cohuck@redhat.com>
On 3/19/21 11:16 AM, Cornelia Huck wrote:
> On Thu, 18 Mar 2021 14:26:24 +0100
> Pierre Morel <pmorel@linux.ibm.com> wrote:
>
>> We need the SCSW definitions to test clear and halt subchannel.
>>
>> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
>> ---
>> lib/s390x/css.h | 23 +++++++++++++++++++++++
>> 1 file changed, 23 insertions(+)
>>
>> diff --git a/lib/s390x/css.h b/lib/s390x/css.h
>> index b0de3a3..460b0bd 100644
>> --- a/lib/s390x/css.h
>> +++ b/lib/s390x/css.h
>> @@ -67,6 +67,29 @@ struct scsw {
>> #define SCSW_SC_PRIMARY 0x00000004
>> #define SCSW_SC_INTERMEDIATE 0x00000008
>> #define SCSW_SC_ALERT 0x00000010
>> +#define SCSW_AC_SUSPEND_PEND 0x00000020
>> +#define SCSW_AC_DEVICE_PEND 0x00000040
>> +#define SCSW_AC_SUBCHANNEL_PEND 0x00000080
>
> Naming: aren't these two rather "active", not "pending"? So maybe
> SCSW_AC_DEVICE_ACTIVE and SCSW_AC_SUBCH_ACTIVE?
right, I modify this
>
>> +#define SCSW_AC_CLEAR_PEND 0x00000100
>> +#define SCSW_AC_HALT_PEND 0x00000200
>> +#define SCSW_AC_START_PEND 0x00000400
>> +#define SCSW_AC_RESUME_PEND 0x00000800
>> +#define SCSW_FC_CLEAR 0x00001000
>> +#define SCSW_FC_HALT 0x00002000
>> +#define SCSW_FC_START 0x00004000
>> +#define SCSW_QDIO_RESERVED 0x00008000
>> +#define SCSW_PATH_NON_OP 0x00010000
>> +#define SCSW_EXTENDED_CTRL 0x00020000
>> +#define SCSW_ZERO_COND 0x00040000
>> +#define SCSW_SUPPRESS_SUSP_INT 0x00080000
>> +#define SCSW_IRB_FMT_CTRL 0x00100000
>> +#define SCSW_INITIAL_IRQ_STATUS 0x00200000
>> +#define SCSW_PREFETCH 0x00400000
>> +#define SCSW_CCW_FORMAT 0x00800000
>> +#define SCSW_DEFERED_CC 0x03000000
>> +#define SCSW_ESW_FORMAT 0x04000000
>> +#define SCSW_SUSPEND_CTRL 0x08000000
>> +#define SCSW_KEY 0xf0000000
>> uint32_t ctrl;
>> uint32_t ccw_addr;
>> #define SCSW_DEVS_DEV_END 0x04
>
--
Pierre Morel
IBM Lab Boeblingen
next prev parent reply other threads:[~2021-03-19 15:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 13:26 [kvm-unit-tests PATCH v1 0/6] Testing SSCH, CSCH and HSCH for errors Pierre Morel
2021-03-18 13:26 ` [kvm-unit-tests PATCH v1 1/6] s390x: lib: css: disabling a subchannel Pierre Morel
2021-03-19 9:02 ` Janosch Frank
2021-03-19 9:11 ` Pierre Morel
2021-03-19 10:03 ` Cornelia Huck
2021-03-19 10:11 ` Pierre Morel
2021-03-19 15:29 ` Pierre Morel
2021-03-18 13:26 ` [kvm-unit-tests PATCH v1 2/6] s390x: lib: css: SCSW bit definitions Pierre Morel
2021-03-19 10:16 ` Cornelia Huck
2021-03-19 15:30 ` Pierre Morel [this message]
2021-03-18 13:26 ` [kvm-unit-tests PATCH v1 3/6] s390x: lib: css: upgrading IRQ handling Pierre Morel
2021-03-18 14:22 ` Pierre Morel
2021-03-19 11:01 ` Cornelia Huck
2021-03-19 15:55 ` Pierre Morel
2021-03-19 16:09 ` Cornelia Huck
2021-03-19 16:34 ` Pierre Morel
2021-03-18 13:26 ` [kvm-unit-tests PATCH v1 4/6] s390x: lib: css: add expectations to wait for interrupt Pierre Morel
2021-03-19 9:09 ` Janosch Frank
2021-03-19 9:50 ` Pierre Morel
2021-03-19 11:23 ` Cornelia Huck
2021-03-19 16:18 ` Pierre Morel
2021-03-18 13:26 ` [kvm-unit-tests PATCH v1 5/6] s390x: css: testing ssch error response Pierre Morel
2021-03-19 9:18 ` Janosch Frank
2021-03-19 10:02 ` Pierre Morel
2021-03-18 13:26 ` [kvm-unit-tests PATCH v1 6/6] s390x: css: testing clear and halt subchannel 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=d39a43c1-4640-1175-31d8-28d90133e63e@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@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;
as well as URLs for NNTP newsgroup(s).