Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>
Cc: kvm@vger.kernel.org, frankja@linux.ibm.com, thuth@redhat.com,
	nsg@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH v3 1/1] s390x: add parallel skey migration test
Date: Wed, 14 Dec 2022 14:42:38 +0100	[thread overview]
Message-ID: <20221214144238.27b886bd@p-imbrenda> (raw)
In-Reply-To: <20221214123814.651451-2-nrb@linux.ibm.com>

On Wed, 14 Dec 2022 13:38:14 +0100
Nico Boehr <nrb@linux.ibm.com> wrote:

> Right now, we have a test which sets storage keys, then migrates the VM
> and - after migration finished - verifies the skeys are still there.
> 
> Add a new version of the test which changes storage keys while the
> migration is in progress. This is achieved by adding a command line
> argument to the existing migration-skey test.

just some small cosmetic issues

> 
> Signed-off-by: Nico Boehr <nrb@linux.ibm.com>
> ---
>  s390x/migration-skey.c | 218 +++++++++++++++++++++++++++++++++++++----
>  s390x/unittests.cfg    |  15 ++-
>  2 files changed, 210 insertions(+), 23 deletions(-)
> 
> diff --git a/s390x/migration-skey.c b/s390x/migration-skey.c
> index a91eb6b5a63e..0f862cc9d821 100644
> --- a/s390x/migration-skey.c
> +++ b/s390x/migration-skey.c
> @@ -2,6 +2,12 @@
>  /*
>   * Storage Key migration tests
>   *
> + * There are two variants of this test:
> + * - sequential: sets some storage keys on pages, migrates the VM and then

"set storage keys on some pages"?
or just "set some storage keys"

> + *   verifies the storage keys are still as we expect.

s/the/that the/

> + * - parallel: start migration of a VM and set and check storage keys on some

s/of a VM/of VM/  or  s/of a VM/of the VM/  or even just  s/of the VM//

> + *   pages while migration is in process.
> + *
>   * Copyright IBM Corp. 2022
>   *
>   * Authors:
> @@ -13,16 +19,45 @@
>  #include <asm/facility.h>
>  #include <asm/page.h>
>  #include <asm/mem.h>
> -#include <asm/interrupt.h>
> +#include <asm/barrier.h>
>  #include <hardware.h>
> +#include <smp.h>
> +

[...]

> +
> +static void print_usage(void)
> +{
> +	report_info("Usage: migration-skey [parallel|sequential]");

--parallel and --sequential

> +}
> +

[...]


  reply	other threads:[~2022-12-14 13:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 12:38 [kvm-unit-tests PATCH v3 0/1] s390x: test storage keys during migration Nico Boehr
2022-12-14 12:38 ` [kvm-unit-tests PATCH v3 1/1] s390x: add parallel skey migration test Nico Boehr
2022-12-14 13:42   ` Claudio Imbrenda [this message]
2022-12-14 18:27   ` Nina Schoetterl-Glausch
2022-12-15  9: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=20221214144238.27b886bd@p-imbrenda \
    --to=imbrenda@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=nrb@linux.ibm.com \
    --cc=nsg@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