public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
	frankja@linux.ibm.com, thuth@redhat.com, david@redhat.com
Subject: Re: [kvm-unit-tests PATCH v3 0/8] s390x: Extend instruction interception tests
Date: Wed, 23 Feb 2022 16:14:40 +0100	[thread overview]
Message-ID: <20220223161440.1eee5eb8@p-imbrenda> (raw)
In-Reply-To: <20220223132940.2765217-1-nrb@linux.ibm.com>

On Wed, 23 Feb 2022 14:29:32 +0100
Nico Boehr <nrb@linux.ibm.com> wrote:

> This series extends the instruction interception tests for s390x.

looks good, I'll queue it, thanks

> 
> 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. 
> 
> Changelog from v2:
> ----
> - Don't run the sck test under PV
> - Include commit of the QEMU PMCW fix in the MSCH and STSCH commit messages
> 
> 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         | 134 +++++++++++++++++++++
>  s390x/unittests.cfg |   7 ++
>  8 files changed, 640 insertions(+)
>  create mode 100644 s390x/epsw.c
>  create mode 100644 s390x/sck.c
> 


      parent reply	other threads:[~2022-02-23 15:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 13:29 [kvm-unit-tests PATCH v3 0/8] s390x: Extend instruction interception tests Nico Boehr
2022-02-23 13:29 ` [kvm-unit-tests PATCH v3 1/8] s390x: Add more tests for MSCH Nico Boehr
2022-02-23 13:29 ` [kvm-unit-tests PATCH v3 2/8] s390x: Add test for PFMF low-address protection Nico Boehr
2022-02-23 13:29 ` [kvm-unit-tests PATCH v3 3/8] s390x: Add sck tests Nico Boehr
2022-02-23 13:29 ` [kvm-unit-tests PATCH v3 4/8] s390x: Add tests for STCRW Nico Boehr
2022-02-23 13:29 ` [kvm-unit-tests PATCH v3 5/8] s390x: Add more tests for SSCH Nico Boehr
2022-02-23 13:29 ` [kvm-unit-tests PATCH v3 6/8] s390x: Add more tests for STSCH Nico Boehr
2022-02-23 15:16   ` Claudio Imbrenda
2022-02-23 15:39   ` Janosch Frank
2022-02-23 17:33     ` Nico Boehr
2022-02-24  0:13       ` Halil Pasic
2022-02-24 10:27     ` Pierre Morel
2022-02-24 10:28       ` Pierre Morel
2022-02-24 14:08     ` Halil Pasic
2022-02-23 13:29 ` [kvm-unit-tests PATCH v3 7/8] s390x: Add tests for TSCH Nico Boehr
2022-02-23 13:29 ` [kvm-unit-tests PATCH v3 8/8] s390x: Add EPSW test Nico Boehr
2022-02-23 15:14 ` Claudio Imbrenda [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=20220223161440.1eee5eb8@p-imbrenda \
    --to=imbrenda@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=frankja@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