public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>,
	kvm@vger.kernel.org, linux-s390@vger.kernel.org
Cc: imbrenda@linux.ibm.com, thuth@redhat.com, david@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2 0/8] s390x: Extend instruction interception tests
Date: Mon, 21 Feb 2022 16:30:32 +0100	[thread overview]
Message-ID: <0bb8a574-059c-f356-fcd1-74d0bc41fa1a@linux.ibm.com> (raw)
In-Reply-To: <20220221130746.1754410-1-nrb@linux.ibm.com>

On 2/21/22 14:07, Nico Boehr wrote:
> This series extends the instruction interception tests for s390x.
> 
> For most instructions, there is already coverage in existing tests, but they are
> not covering some failure cases, e.g. bad alignment. In this case, the existing
> tests were extended.
> 
> SCK was not under test anywhere yet, hence a new test file was added.
> 
> The EPSW test gets it's own file, too, because it requires a I/O device, more
> details in the respective commit.

Could you please push this to devel so we can get CI data?

To me it seems like only STSCH needs review so we should be done with 
this soonish.


> 
> Changelog from v1:
> ----
> - Reset pmcw flags at test end
> - Rebase
> 
> Nico Boehr (8):
>    s390x: Add more tests for MSCH
>    s390x: Add test for PFMF low-address protection
>    s390x: Add sck tests
>    s390x: Add tests for STCRW
>    s390x: Add more tests for SSCH
>    s390x: Add more tests for STSCH
>    s390x: Add tests for TSCH
>    s390x: Add EPSW test
> 
>   lib/s390x/css.h     |  17 +++
>   lib/s390x/css_lib.c |  60 ++++++++++
>   s390x/Makefile      |   2 +
>   s390x/css.c         | 278 ++++++++++++++++++++++++++++++++++++++++++++
>   s390x/epsw.c        | 113 ++++++++++++++++++
>   s390x/pfmf.c        |  29 +++++
>   s390x/sck.c         | 127 ++++++++++++++++++++
>   s390x/unittests.cfg |   7 ++
>   8 files changed, 633 insertions(+)
>   create mode 100644 s390x/epsw.c
>   create mode 100644 s390x/sck.c
> 


  parent reply	other threads:[~2022-02-21 15:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 13:07 [kvm-unit-tests PATCH v2 0/8] s390x: Extend instruction interception tests Nico Boehr
2022-02-21 13:07 ` [kvm-unit-tests PATCH v2 1/8] s390x: Add more tests for MSCH Nico Boehr
2022-02-21 13:07 ` [kvm-unit-tests PATCH v2 2/8] s390x: Add test for PFMF low-address protection Nico Boehr
2022-02-21 13:07 ` [kvm-unit-tests PATCH v2 3/8] s390x: Add sck tests Nico Boehr
2022-02-21 13:07 ` [kvm-unit-tests PATCH v2 4/8] s390x: Add tests for STCRW Nico Boehr
2022-02-21 13:07 ` [kvm-unit-tests PATCH v2 5/8] s390x: Add more tests for SSCH Nico Boehr
2022-02-21 13:07 ` [kvm-unit-tests PATCH v2 6/8] s390x: Add more tests for STSCH Nico Boehr
2022-02-21 13:07 ` [kvm-unit-tests PATCH v2 7/8] s390x: Add tests for TSCH Nico Boehr
2022-02-21 13:07 ` [kvm-unit-tests PATCH v2 8/8] s390x: Add EPSW test Nico Boehr
2022-02-21 15:30 ` Janosch Frank [this message]
2022-02-23  9:18   ` [kvm-unit-tests PATCH v2 0/8] s390x: Extend instruction interception tests Nico Boehr

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=0bb8a574-059c-f356-fcd1-74d0bc41fa1a@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=nrb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox