From: Cornelia Huck <cohuck@redhat.com>
To: Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v1 1/1] s390x: fix storage attributes migration for non-small guests
Date: Thu, 18 Jan 2018 17:20:34 +0100 [thread overview]
Message-ID: <20180118172034.3dda2622.cohuck@redhat.com> (raw)
In-Reply-To: <1516035122-7617-1-git-send-email-imbrenda@linux.vnet.ibm.com>
On Mon, 15 Jan 2018 17:52:02 +0100
Claudio Imbrenda <imbrenda@linux.vnet.ibm.com> wrote:
> Fix storage attribute migration so that it does not fail for guests
> with more than a few GB of RAM. Migration itself was successful, but
> storage attributes were not migrated completely.
>
> This patch fixes the migration of all storage attributes, even when the
> guest have large amounts of memory.
>
> Signed-off-by: Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>
> Fixes: 903fd80b03243476 ("s390x/migration: Storage attributes device")
> ---
> hw/s390x/s390-stattrib-kvm.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/s390x/s390-stattrib-kvm.c b/hw/s390x/s390-stattrib-kvm.c
> index 41770a7..480551c 100644
> --- a/hw/s390x/s390-stattrib-kvm.c
> +++ b/hw/s390x/s390-stattrib-kvm.c
> @@ -116,7 +116,7 @@ static void kvm_s390_stattrib_synchronize(S390StAttribState *sa)
> for (cx = 0; cx + len <= max; cx += len) {
> clog.start_gfn = cx;
> clog.count = len;
> - clog.values = (uint64_t)(sas->incoming_buffer + cx * len);
Hm, doesn't that even imply that you reference an area beyond the
buffer, as the <= max check does not catch this?
> + clog.values = (uint64_t)(sas->incoming_buffer + cx);
> r = kvm_vm_ioctl(kvm_state, KVM_S390_SET_CMMA_BITS, &clog);
> if (r) {
> error_report("KVM_S390_SET_CMMA_BITS failed: %s", strerror(-r));
> @@ -126,7 +126,7 @@ static void kvm_s390_stattrib_synchronize(S390StAttribState *sa)
> if (cx < max) {
> clog.start_gfn = cx;
> clog.count = max - cx;
> - clog.values = (uint64_t)(sas->incoming_buffer + cx * len);
> + clog.values = (uint64_t)(sas->incoming_buffer + cx);
> r = kvm_vm_ioctl(kvm_state, KVM_S390_SET_CMMA_BITS, &clog);
> if (r) {
> error_report("KVM_S390_SET_CMMA_BITS failed: %s", strerror(-r));
next prev parent reply other threads:[~2018-01-18 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 16:52 [Qemu-devel] [PATCH v1 1/1] s390x: fix storage attributes migration for non-small guests Claudio Imbrenda
2018-01-15 18:53 ` Christian Borntraeger
2018-01-18 16:20 ` Cornelia Huck [this message]
2018-01-18 16:52 ` Claudio Imbrenda
2018-01-18 17:02 ` Cornelia Huck
2018-01-18 17:23 ` Claudio Imbrenda
2018-01-18 17:25 ` Cornelia Huck
2018-01-18 17:33 ` Claudio Imbrenda
2018-01-18 17:40 ` 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=20180118172034.3dda2622.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=imbrenda@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
/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).