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 v5 0/6] CSS Mesurement Block
Date: Thu, 11 Mar 2021 11:19:32 +0100 [thread overview]
Message-ID: <a9d290eb-cc81-1e1e-ae38-8e2aa6307b68@linux.ibm.com> (raw)
In-Reply-To: <20210309180834.14945da1.cohuck@redhat.com>
On 3/9/21 6:08 PM, Cornelia Huck wrote:
> On Tue, 9 Mar 2021 17:54:01 +0100
> Cornelia Huck <cohuck@redhat.com> wrote:
>
>> On Tue, 9 Mar 2021 13:51:11 +0100
>> Pierre Morel <pmorel@linux.ibm.com> wrote:
>>
>>> We tests the update of the Mesurement Block (MB) format 0
>>> and format 1 using a serie of senseid requests.
>>>
>>> *Warning*: One of the tests for format-1 will unexpectedly fail for QEMU elf
>>> unless the QEMU patch "css: SCHIB measurement block origin must be aligned"
>>> is applied.
>>
>> That one has hit QEMU master by now.
>>
>>> With Protected Virtualization, the PGM is correctly recognized.
>>>
>>> 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.
>>> - failures not part of the feature under test will stop the tests.
>>> - we add a css_enabled() function to test if a subchannel is enabled.
>>>
>>> *note*:
>>> I rearranged the use of the senseid for the tests, by not modifying
>>> the existing test and having a dedicated senseid() function for
>>> the purpose of the tests.
>>> I think that it is in the rigght way so I kept the RB and ACK on
>>> the simplification, there are less changes, if it is wrong from me
>>> I suppose I will see this in the comments.
>>> Since the changed are moved inside the fmt0 test which is not approved
>>> for now I hope it is OK.
>>
>> I'll double-check, but I think it should be ok.
>
> ...that said, I found some reordering issues, but nothing major;
> generally, it looks good to me.
Thanks,
so I do the reordering and respin for hopefully the right series :)
Regards,
Pierre
--
Pierre Morel
IBM Lab Boeblingen
prev parent reply other threads:[~2021-03-11 10:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 12:51 [kvm-unit-tests PATCH v5 0/6] CSS Mesurement Block Pierre Morel
2021-03-09 12:51 ` [kvm-unit-tests PATCH v5 1/6] s390x: css: Store CSS Characteristics Pierre Morel
2021-03-09 12:51 ` [kvm-unit-tests PATCH v5 2/6] s390x: css: simplifications of the tests Pierre Morel
2021-03-09 12:51 ` [kvm-unit-tests PATCH v5 3/6] s390x: css: extending the subchannel modifying functions Pierre Morel
2021-03-09 12:51 ` [kvm-unit-tests PATCH v5 4/6] s390x: css: implementing Set CHannel Monitor Pierre Morel
2021-03-09 16:56 ` Cornelia Huck
2021-03-11 10:20 ` Pierre Morel
2021-03-09 12:51 ` [kvm-unit-tests PATCH v5 5/6] s390x: css: testing measurement block format 0 Pierre Morel
2021-03-09 17:05 ` Cornelia Huck
2021-03-11 10:26 ` Pierre Morel
2021-03-09 12:51 ` [kvm-unit-tests PATCH v5 6/6] s390x: css: testing measurement block format 1 Pierre Morel
2021-03-09 17:07 ` Cornelia Huck
2021-03-11 10:26 ` Pierre Morel
2021-03-09 16:54 ` [kvm-unit-tests PATCH v5 0/6] CSS Mesurement Block Cornelia Huck
2021-03-09 17:08 ` Cornelia Huck
2021-03-11 10:19 ` Pierre Morel [this message]
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=a9d290eb-cc81-1e1e-ae38-8e2aa6307b68@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