From: Cornelia Huck <cohuck@redhat.com>
To: Pierre Morel <pmorel@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
frankja@linux.ibm.com, david@redhat.com, thuth@redhat.com,
imbrenda@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH v1 5/5] s390x: css: testing measurement block format 1
Date: Tue, 2 Feb 2021 12:52:09 +0100 [thread overview]
Message-ID: <20210202125209.4ef8b66c.cohuck@redhat.com> (raw)
In-Reply-To: <1611930869-25745-6-git-send-email-pmorel@linux.ibm.com>
On Fri, 29 Jan 2021 15:34:29 +0100
Pierre Morel <pmorel@linux.ibm.com> wrote:
> Measurement block format 1 is made available by the extended
> mesurement block facility and is indicated in the SCHIB by
> the bit in the PMCW.
>
> The MBO is specified in the SCHIB of each channel and the MBO
> defined by the SCHM instruction is ignored.
>
> The test of the MB format 1 is just skip if the feature is
s/skip/skipped/
> not available.
>
> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
> ---
> s390x/css.c | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 51 insertions(+)
>
(...)
> @@ -208,6 +251,14 @@ static void test_schm(void)
> schm(mb0, SCHM_MBU);
> test_schm_fmt0(mb0);
>
> + mb1 = alloc_io_mem(sizeof(struct measurement_block_format1), 0);
> + if (!mb1) {
I'm wondering whether you should move this into the format 1
invocation, so you won't try to allocate memory if format 1 is not even
supported.
> + report(0, "mesurement_block_format0 allocation");
In any case, s/mesurement_block_format0/measurement_block_format1/ :)
> + goto end_free;
> + }
> + test_schm_fmt1(mb1);
> +
> + free_io_mem(mb1, sizeof(struct measurement_block_format1));
> end_free:
> free_io_mem(mb0, sizeof(struct measurement_block_format0));
> }
next prev parent reply other threads:[~2021-02-02 11:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1611930869-25745-1-git-send-email-pmorel@linux.ibm.com>
[not found] ` <1611930869-25745-4-git-send-email-pmorel@linux.ibm.com>
2021-02-02 11:48 ` [kvm-unit-tests PATCH v1 3/5] s390x: css: implementing Set CHannel Monitor Cornelia Huck
2021-02-02 16:15 ` Pierre Morel
2021-02-02 17:32 ` Thomas Huth
2021-02-03 10:09 ` Pierre Morel
[not found] ` <1611930869-25745-6-git-send-email-pmorel@linux.ibm.com>
2021-02-02 11:52 ` Cornelia Huck [this message]
[not found] ` <1611930869-25745-2-git-send-email-pmorel@linux.ibm.com>
2021-02-01 10:01 ` [kvm-unit-tests PATCH v1 1/5] s390x: css: Store CSS Characteristics Janosch Frank
2021-02-01 12:09 ` Pierre Morel
2021-02-02 11:11 ` Cornelia Huck
2021-02-02 14:19 ` Pierre Morel
2021-02-02 17:25 ` Thomas Huth
2021-02-03 10:12 ` Pierre Morel
[not found] ` <1611930869-25745-3-git-send-email-pmorel@linux.ibm.com>
2021-02-01 10:11 ` [kvm-unit-tests PATCH v1 2/5] s390x: css: simplifications of the tests Janosch Frank
2021-02-01 12:15 ` Pierre Morel
2021-02-01 12:22 ` Janosch Frank
2021-02-02 11:23 ` Cornelia Huck
2021-02-02 14:39 ` Pierre Morel
2021-02-02 17:29 ` Thomas Huth
2021-02-03 10:10 ` Pierre Morel
[not found] ` <1611930869-25745-5-git-send-email-pmorel@linux.ibm.com>
2021-02-02 17:35 ` [kvm-unit-tests PATCH v1 4/5] s390x: css: SCHM tests format 0 Thomas Huth
2021-02-03 10:09 ` 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=20210202125209.4ef8b66c.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.