From: David Hildenbrand <dahi@linux.vnet.ibm.com>
To: Thomas Huth <thuth@redhat.com>, jjherne@linux.vnet.ibm.com
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
borntraeger@de.ibm.com, jfrei@linux.vnet.ibm.com,
qemu-devel@nongnu.org, agraf@suse.de
Subject: Re: [Qemu-devel] [PATCH for-2.5 7/8] s390x: Migrate guest storage keys (initial memory only)
Date: Tue, 21 Jul 2015 12:37:18 +0200 [thread overview]
Message-ID: <20150721123718.6ab0b668@thinkpad-w530> (raw)
In-Reply-To: <55ADFE0B.1090407@redhat.com>
>
> So if I've got this code right, you send here a "header" that announces
> a packet with all pages ...
>
> > + while (handled_count < total_count) {
> > + cur_count = MIN(total_count - handled_count, S390_SKEYS_BUFFER_SIZE);
> > +
> > + ret = skeyclass->get_skeys(ss, cur_gfn, cur_count, buf);
> > + if (ret < 0) {
> > + error_report("S390_GET_KEYS error %d\n", ret);
> > + break;
>
> ... but when an error occurs here, you suddenly stop in the middle of
> that "packet" with all pages ...
Indeed, although that should never fail, we never know.
We don't want to overengineer the protocol but still abort migration at least
on the loading side in that (theoretical) case.
>
> > + }
> > +
> > + /* write keys to stream */
> > + qemu_put_buffer(f, buf, cur_count);
> > +
> > + cur_gfn += cur_count;
> > + handled_count += cur_count;
> > + }
> > +
> > + g_free(buf);
> > +end_stream:
> > + qemu_put_be64(f, S390_SKEYS_SAVE_FLAG_EOS);
>
> ... and send an EOS marker here instead ...
>
> > +}
> > +
> > +static int s390_storage_keys_load(QEMUFile *f, void *opaque, int version_id)
> > +{
> > + S390SKeysState *ss = S390_SKEYS(opaque);
> > + S390SKeysClass *skeyclass = S390_SKEYS_GET_CLASS(ss);
> > + int ret = 0;
> > +
> > + while (!ret) {
> > + ram_addr_t addr;
> > + int flags;
> > +
> > + addr = qemu_get_be64(f);
> > + flags = addr & ~TARGET_PAGE_MASK;
> > + addr &= TARGET_PAGE_MASK;
> > +
> > + switch (flags) {
> > + case S390_SKEYS_SAVE_FLAG_SKEYS: {
> > + const uint64_t total_count = qemu_get_be64(f);
> > + uint64_t handled_count = 0, cur_count;
> > + uint64_t cur_gfn = addr / TARGET_PAGE_SIZE;
> > + uint8_t *buf = g_try_malloc(S390_SKEYS_BUFFER_SIZE);
> > +
> > + if (!buf) {
> > + error_report("storage key load could not allocate memory\n");
> > + ret = -ENOMEM;
> > + break;
> > + }
> > +
> > + while (handled_count < total_count) {
> > + cur_count = MIN(total_count - handled_count,
> > + S390_SKEYS_BUFFER_SIZE);
> > + qemu_get_buffer(f, buf, cur_count);
>
> ... while the receiver can not handle the EOS marker here.
>
> This looks fishy to me (or I might have just missed something), but
> anyway please double check whether your error handling in the sender
> really makes sense.
My shot would be, to send invalid storage keys if getting the keys from the
kernel fails. So we can detect it on the loading side and abort migration
gracefully.
>
> > + ret = skeyclass->set_skeys(ss, cur_gfn, cur_count, buf);
> > + if (ret < 0) {
> > + error_report("S390_SET_KEYS error %d\n", ret);
> > + break;
> > + }
> > + handled_count += cur_count;
> > + cur_gfn += cur_count;
> > + }
> > + g_free(buf);
> > + break;
> > + }
> > + case S390_SKEYS_SAVE_FLAG_EOS:
> > + /* normal exit */
> > + return 0;
> > + default:
> > + error_report("Unexpected storage key flag data: %#x", flags);
> > + ret = -EINVAL;
> > + }
> > + }
> > +
> > + return ret;
> > +}
>
> Thomas
Thanks Thomas!
David
next prev parent reply other threads:[~2015-07-21 10:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 13:49 [Qemu-devel] [PATCH for-2.5 0/8] s390x: storage key migration Cornelia Huck
2015-07-20 13:49 ` [Qemu-devel] [PATCH for-2.5 1/8] s390x: add 2.5 compat s390-ccw-virtio machine Cornelia Huck
2015-07-20 13:58 ` Christian Borntraeger
2015-07-20 13:49 ` [Qemu-devel] [PATCH for-2.5 2/8] s390x: Create QOM device for s390 storage keys Cornelia Huck
2015-07-20 13:49 ` [Qemu-devel] [PATCH for-2.5 3/8] s390x: Enable new s390-storage-keys device Cornelia Huck
2015-07-20 13:49 ` [Qemu-devel] [PATCH for-2.5 4/8] s390x: Dump storage keys qmp command Cornelia Huck
2015-07-20 14:32 ` Eric Blake
2015-07-20 13:49 ` [Qemu-devel] [PATCH for-2.5 5/8] s390x: Dump-skeys hmp support Cornelia Huck
2015-07-20 13:49 ` [Qemu-devel] [PATCH for-2.5 6/8] s390x: Info skeys sub-command Cornelia Huck
2015-07-20 13:49 ` [Qemu-devel] [PATCH for-2.5 7/8] s390x: Migrate guest storage keys (initial memory only) Cornelia Huck
2015-07-21 8:08 ` Thomas Huth
2015-07-21 10:37 ` David Hildenbrand [this message]
2015-07-30 15:00 ` Jason J. Herne
2015-07-30 15:12 ` Thomas Huth
2015-08-13 14:11 ` Jason J. Herne
2015-08-13 15:44 ` Christian Borntraeger
2015-07-20 13:49 ` [Qemu-devel] [PATCH for-2.5 8/8] s390x: Disable storage key migration on old machine type Cornelia Huck
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=20150721123718.6ab0b668@thinkpad-w530 \
--to=dahi@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--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;
as well as URLs for NNTP newsgroup(s).