public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: Nico Boehr <nrb@linux.ibm.com>,
	kvm@vger.kernel.org, linux-s390@vger.kernel.org,
	thuth@redhat.com, scgl@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH v4 1/1] s390x: add migration test for storage keys
Date: Fri, 10 Jun 2022 13:56:38 +0200	[thread overview]
Message-ID: <20220610135638.2c4f6b1d@p-imbrenda> (raw)
In-Reply-To: <2fc9f517-57d0-73ae-3083-26e5dcf05dbb@linux.ibm.com>

On Fri, 10 Jun 2022 10:49:28 +0200
Janosch Frank <frankja@linux.ibm.com> wrote:

[...]

> > +		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);
> > +
> > +		actual_key.val = get_storage_key(pagebuf[i]);  
> 
> iske is nice but I think it would also be interesting to check if the 
> actual memory protection was carried over. The iske check is enough for 
> now though.

we had that in a previous version, but I think it's overkill, there are
separate tests to check for key protection, I think?

also, under TCG the value of the storage keys is migrated, but there is
no protection, this makes the test unnecessarily complex

[...]

  reply	other threads:[~2022-06-10 11:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 13:13 [kvm-unit-tests PATCH v4 0/1] s390x: add migration test for storage keys Nico Boehr
2022-06-08 13:13 ` [kvm-unit-tests PATCH v4 1/1] " Nico Boehr
2022-06-10  8:49   ` Janosch Frank
2022-06-10 11:56     ` Claudio Imbrenda [this message]
2022-06-13  9:19     ` [kvm-unit-tests PATCH v4 1/1] s390x: add migration test for storage keys:q! Nico Boehr
2022-06-08 13:39 ` [kvm-unit-tests PATCH v4 0/1] s390x: add migration test for storage keys 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=20220610135638.2c4f6b1d@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=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