From: Pierre Morel <pmorel@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, frankja@linux.ibm.com,
david@redhat.com, thuth@redhat.com, cohuck@redhat.com,
imbrenda@linux.ibm.com
Subject: [kvm-unit-tests PATCH v2 0/5] CSS Mesurement Block
Date: Wed, 10 Feb 2021 14:20:09 +0100 [thread overview]
Message-ID: <1612963214-30397-1-git-send-email-pmorel@linux.ibm.com> (raw)
We tests the update of the Mesurement Block (MB) format 0
and format 1 using a serie of senseid requests.
The MB format 1 is only provided if the Extended mesurement Block
feature is available.
This feature is exposed by the CSS characteristics general features
stored by the Store Channel Subsystem Characteristics CHSC command,
consequently, we implement the CHSC instruction call and the SCSC CHSC
command.
In order to ease the writing of new tests using:
- interrupt
- enablement of a subchannel
- multiple I/O on a subchannel
We do the following simplifications:
- we create a CSS initialization routine
- we register the I/O interrupt handler on CSS initialization
- we do not enable or disable a subchannel in the senseid test,
assuming this test is done after the enable test, this allows
to create traffic using the SSCH used by senseid.
- we add a css_enabled() function to test if a subchannel is enabled.
Regards,
Pierre
Pierre Morel (5):
s390x: css: Store CSS Characteristics
s390x: css: simplifications of the tests
s390x: css: implementing Set CHannel Monitor
s390x: css: testing measurement block format 0
s390x: css: testing measurement block format 1
lib/s390x/css.h | 117 ++++++++++++++++++++++-
lib/s390x/css_lib.c | 223 +++++++++++++++++++++++++++++++++++++++++---
s390x/css.c | 186 ++++++++++++++++++++++++++++++++----
3 files changed, 493 insertions(+), 33 deletions(-)
--
2.17.1
changelog:
from v1:
- check the return code of CHSC
(Connie)
- reporting in css_init
(Connie)
- added braces when a loop contains several statement
(Thomas)
- changed retval to success in boolean function
(Thomas)
- suppress goto retries
(thomas)
- rewording and use correct return types in css_enabled
(Janosch)
next reply other threads:[~2021-02-10 13:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 13:20 Pierre Morel [this message]
2021-02-10 13:20 ` [kvm-unit-tests PATCH v2 1/5] s390x: css: Store CSS Characteristics Pierre Morel
2021-02-12 10:32 ` Cornelia Huck
2021-02-12 15:35 ` Pierre Morel
2021-02-10 13:20 ` [kvm-unit-tests PATCH v2 2/5] s390x: css: simplifications of the tests Pierre Morel
2021-02-12 10:36 ` Cornelia Huck
2021-02-12 15:36 ` Pierre Morel
2021-02-10 13:20 ` [kvm-unit-tests PATCH v2 3/5] s390x: css: implementing Set CHannel Monitor Pierre Morel
2021-02-12 10:53 ` Cornelia Huck
2021-02-12 15:51 ` Pierre Morel
2021-02-10 13:20 ` [kvm-unit-tests PATCH v2 4/5] s390x: css: testing measurement block format 0 Pierre Morel
2021-02-12 11:12 ` Cornelia Huck
2021-02-12 15:59 ` Pierre Morel
2021-02-10 13:20 ` [kvm-unit-tests PATCH v2 5/5] s390x: css: testing measurement block format 1 Pierre Morel
2021-02-12 11:15 ` Cornelia Huck
2021-02-12 16:04 ` 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=1612963214-30397-1-git-send-email-pmorel@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=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;
as well as URLs for NNTP newsgroup(s).