From: Nico Boehr <nrb@linux.ibm.com>
To: Janis Schoetterl-Glausch <scgl@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org
Cc: frankja@linux.ibm.com, imbrenda@linux.ibm.com, thuth@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2 1/1] s390x: add migration test for storage keys
Date: Tue, 17 May 2022 10:17:22 +0200 [thread overview]
Message-ID: <3ab95d5d553362a686b9526c8b53996dcaf20400.camel@linux.ibm.com> (raw)
In-Reply-To: <947af627-64e0-486d-18e2-c877bc4c4ba6@linux.ibm.com>
On Mon, 2022-05-16 at 18:47 +0200, Janis Schoetterl-Glausch wrote:
> On 5/16/22 11:07, Nico Boehr wrote:
> > Upon migration, we expect storage keys being set by the guest to be
> > preserved,
> > so add a test for it.
>
> "being set" implies that keys are set while the migration is going
> on.
> That's not the case, is it?
Fixed.
> > We keep 128 pages and set predictable storage keys. Then, we
> > migrate and check
> > they can be read back and the respective access restrictions are in
> > place when
>
> ... check that they ...
Added that.
>
> > the access key in the PSW doesn't match.
>
> The latter half of the sentence doesn't apply anymore, now that you
> simplified the test.
> So maybe something like: ... and check that they can be read back and
> match the value
> originally set.
Fixed.
> > diff --git a/s390x/migration-skey.c b/s390x/migration-skey.c
> > new file mode 100644
> > index 000000000000..ee4622eb94ba
> > --- /dev/null
> > +++ b/s390x/migration-skey.c
> > @@ -0,0 +1,78 @@
> > +/* SPDX-License-Identifier: GPL-2.0-only */
> > +/*
> > + * Storage Key migration tests
> > + *
> > + * Copyright IBM Corp. 2022
> > + *
> > + * Authors:
> > + * Nico Boehr <nrb@linux.ibm.com>
> > + */
> > +
> > +#include <libcflat.h>
> > +#include <asm/facility.h>
> > +#include <asm/page.h>
> > +#include <asm/mem.h>
> > +#include <asm/interrupt.h>
> > +#include <hardware.h>
> > +
> > +#define NUM_PAGES 128
> > +static uint8_t pagebuf[NUM_PAGES][PAGE_SIZE]
> > __attribute__((aligned(PAGE_SIZE)));
> > +
> > +static void test_migration(void)
> > +{
> > + int i, key_to_set;
> > + uint8_t *page;
> > + union skey expected_key, actual_key;
> > +
> > + for (i = 0; i < NUM_PAGES; i++) {
> > + /*
> > + * Storage keys are 7 bit, lowest bit is always
> > returned as zero
> > + * by iske
> > + */
> > + key_to_set = i * 2;
> > + set_storage_key(pagebuf[i], key_to_set, 1);
> > + }
> > +
> > + puts("Please migrate me, then press return\n");
> > + (void)getchar();
> > +
> > + for (i = 0; i < NUM_PAGES; i++) {
> > + report_prefix_pushf("page %d", i);
> > +
> > + page = &pagebuf[i][0];
> > + actual_key.val = get_storage_key(page);
>
> The page variable is kinda useless now, I'd just do
> get_storage_key(pagebuf[0]).
Removed.
> > + expected_key.val = i * 2;
> > +
> > + /* ignore reference bit */
>
> Why? Are there any implicit references I'm missing?
Since the PoP specifies (p. 5-122):
"The record of references provided by the reference
bit is not necessarily accurate. However, in the major-
ity of situations, reference recording approximately
coincides with the related storage reference."
I don't really see a way to test this properly.
Maybe I missed something?
next prev parent reply other threads:[~2022-05-17 8:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 9:07 [kvm-unit-tests PATCH v2 0/1] s390x: add migration test for storage keys Nico Boehr
2022-05-16 9:07 ` [kvm-unit-tests PATCH v2 1/1] " Nico Boehr
2022-05-16 15:59 ` Claudio Imbrenda
2022-05-16 16:47 ` Janis Schoetterl-Glausch
2022-05-17 8:17 ` Nico Boehr [this message]
2022-05-17 11:44 ` Janis Schoetterl-Glausch
2022-05-17 11:53 ` Nico Boehr
2022-05-17 12:29 ` Claudio Imbrenda
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=3ab95d5d553362a686b9526c8b53996dcaf20400.camel@linux.ibm.com \
--to=nrb@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=scgl@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