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 4/5] s390x: css: testing measurement block format 0
Date: Tue, 23 Feb 2021 17:05:12 +0100 [thread overview]
Message-ID: <20210223170512.39db5cab.cohuck@redhat.com> (raw)
In-Reply-To: <c0af463a-d5ae-d84e-7a37-217bed4aeb78@linux.ibm.com>
On Tue, 23 Feb 2021 16:49:56 +0100
Pierre Morel <pmorel@linux.ibm.com> wrote:
> On 2/23/21 2:27 PM, Cornelia Huck wrote:
> > On Thu, 18 Feb 2021 18:26:43 +0100
> > Pierre Morel <pmorel@linux.ibm.com> wrote:
> >> + */
> >> +static void test_schm_fmt0(void)
> >> +{
> >> + struct measurement_block_format0 *mb0;
> >> + int shared_mb_size = 2 * sizeof(struct measurement_block_format0);
> >> +
> >> + report_prefix_push("Format 0");
> >> +
> >> + /* Allocate zeroed Measurement block */
> >> + mb0 = alloc_io_mem(shared_mb_size, 0);
> >> + if (!mb0) {
> >> + report_abort("measurement_block_format0 allocation failed");
> >> + goto end;
> >> + }
> >> +
> >> + schm(NULL, 0); /* Stop any previous measurement */
> >
> > Probably not strictly needed, but cannot hurt.
> yes
>
> >
> >> + schm(mb0, SCHM_MBU);
> >> +
> >> + /* Expect success */
> >> + report_prefix_push("Valid MB address and index 0");
> >> + report(start_measure(0, 0, false) &&
> >> + mb0->ssch_rsch_count == SCHM_UPDATE_CNT,
> >> + "SSCH measured %d", mb0->ssch_rsch_count);
> >> + report_prefix_pop();
> >> +
> >> + /* Clear the measurement block for the next test */
> >> + memset(mb0, 0, shared_mb_size);
> >> +
> >> + /* Expect success */
> >> + report_prefix_push("Valid MB address and index 1");
> >> + report(start_measure(0, 1, false) &&
> >> + mb0[1].ssch_rsch_count == SCHM_UPDATE_CNT,
> >> + "SSCH measured %d", mb0[1].ssch_rsch_count);
> >> + report_prefix_pop();
> >> +
> >> + schm(NULL, 0); /* Stop the measurement */
> >
> > Shouldn't you call css_disable_mb() here as well?
>
> I do not think it is obligatory, measurements are stopped but it may be
> indeed better so we get a clean SCHIB.
> So yes,
>
> css_disable_mb();
> schm(NULL, 0);
>
> seems the right thing to do.
Yes, keeping a reference to something you free seems just wrong.
next prev parent reply other threads:[~2021-02-23 16:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 17:26 [kvm-unit-tests PATCH v3 0/5] CSS Mesurement Block Pierre Morel
2021-02-18 17:26 ` [kvm-unit-tests PATCH v3 1/5] s390x: css: Store CSS Characteristics Pierre Morel
2021-02-26 9:50 ` Janosch Frank
2021-02-26 13:38 ` Pierre Morel
2021-02-18 17:26 ` [kvm-unit-tests PATCH v3 2/5] s390x: css: simplifications of the tests Pierre Morel
2021-02-18 17:26 ` [kvm-unit-tests PATCH v3 3/5] s390x: css: implementing Set CHannel Monitor Pierre Morel
2021-02-23 13:22 ` Cornelia Huck
2021-02-23 15:43 ` Pierre Morel
2021-02-18 17:26 ` [kvm-unit-tests PATCH v3 4/5] s390x: css: testing measurement block format 0 Pierre Morel
2021-02-23 13:27 ` Cornelia Huck
2021-02-23 15:49 ` Pierre Morel
2021-02-23 16:05 ` Cornelia Huck [this message]
2021-02-18 17:26 ` [kvm-unit-tests PATCH v3 5/5] s390x: css: testing measurement block format 1 Pierre Morel
2021-02-23 13:29 ` Cornelia Huck
2021-02-23 15:52 ` Pierre Morel
2021-02-26 10:02 ` Janosch Frank
2021-02-26 13:34 ` 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=20210223170512.39db5cab.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 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.