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
Subject: Re: [kvm-unit-tests PATCH v1 0/2] s390x: add migration test for CMM
Date: Mon, 9 May 2022 16:00:09 +0200	[thread overview]
Message-ID: <20220509160009.3d90cbe4@p-imbrenda> (raw)
In-Reply-To: <20220509120805.437660-1-nrb@linux.ibm.com>

On Mon,  9 May 2022 14:08:03 +0200
Nico Boehr <nrb@linux.ibm.com> wrote:

> Upon migration, we expect the CMM page states to be preserved. Add a test which
> checks for that.
> 
> The new test gets a new file so the existing cmm test can still run when the
> prerequisites for running migration tests aren't given (netcat). Therefore, move

I wonder if we are going to have more of these "split" tests.

is there a way to make sure migration prerequisites are always present?
or rewrite things so that we don't need them?

> some definitions to a common header to be able to re-use them.
> 
> Nico Boehr (2):
>   lib: s390x: add header for CMM related defines
>   s390x: add cmm migration test
> 
>  lib/s390x/asm/cmm.h   | 50 +++++++++++++++++++++++++++
>  s390x/Makefile        |  1 +
>  s390x/cmm-migration.c | 78 +++++++++++++++++++++++++++++++++++++++++++
>  s390x/cmm.c           | 25 ++------------
>  s390x/unittests.cfg   |  4 +++
>  5 files changed, 136 insertions(+), 22 deletions(-)
>  create mode 100644 lib/s390x/asm/cmm.h
>  create mode 100644 s390x/cmm-migration.c
> 


  parent reply	other threads:[~2022-05-09 14:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09 12:08 [kvm-unit-tests PATCH v1 0/2] s390x: add migration test for CMM Nico Boehr
2022-05-09 12:08 ` [kvm-unit-tests PATCH v1 1/2] lib: s390x: add header for CMM related defines Nico Boehr
2022-05-09 12:08 ` [kvm-unit-tests PATCH v1 2/2] s390x: add cmm migration test Nico Boehr
2022-05-09 13:58   ` Claudio Imbrenda
2022-05-10 13:25     ` Nico Boehr
2022-05-10 13:45       ` Claudio Imbrenda
2022-05-10 14:13         ` Nico Boehr
2022-05-09 14:00 ` Claudio Imbrenda [this message]
2022-05-10 10:58   ` [kvm-unit-tests PATCH v1 0/2] s390x: add migration test for CMM Nico Boehr
2022-05-10 12:47     ` Janosch Frank
2022-05-11  8:59       ` 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=20220509160009.3d90cbe4@p-imbrenda \
    --to=imbrenda@linux.ibm.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