From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34900) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fk9Fv-0003NB-Iq for qemu-devel@nongnu.org; Mon, 30 Jul 2018 10:34:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fk9Fs-0003CB-CR for qemu-devel@nongnu.org; Mon, 30 Jul 2018 10:34:39 -0400 References: <1532959766-53343-1-git-send-email-borntraeger@de.ibm.com> From: David Hildenbrand Message-ID: <1bf75ad8-dc90-b94e-0ead-53fdbc72dd4f@redhat.com> Date: Mon, 30 Jul 2018 16:34:33 +0200 MIME-Version: 1.0 In-Reply-To: <1532959766-53343-1-git-send-email-borntraeger@de.ibm.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH 1/1] s390x/sclp: fix maxram calculation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Christian Borntraeger , Cornelia Huck Cc: qemu-devel , qemu-s390x , Alexander Graf , Thomas Huth , Richard Henderson , Janosch Frank , Halil Pasic , imbrenda@linux.vnet.ibm.com On 30.07.2018 16:09, Christian Borntraeger wrote: > We clamp down ram_size to match the sclp increment size. We do > not do the same for maxram_size, which means for large guests > with some sizes (e.g. -m 50000) maxram_size differs from ram_size. > This can break other code (e.g. CMMA migration) which uses maxram_size > to calculate the number of pages and then throws some errors. So the only problem is that the buffer size between source and target differ? >=20 > Fixes: 82fab5c5b90e468f3e9d54c ("s390x/sclp: remove memory hotplug supp= ort") > Signed-off-by: Christian Borntraeger > CC: qemu-stable@nongnu.org > CC: David Hildenbrand > --- > hw/s390x/sclp.c | 1 + > 1 file changed, 1 insertion(+) >=20 > diff --git a/hw/s390x/sclp.c b/hw/s390x/sclp.c > index bd2a024..4510a80 100644 > --- a/hw/s390x/sclp.c > +++ b/hw/s390x/sclp.c > @@ -320,6 +320,7 @@ static void sclp_memory_init(SCLPDevice *sclp) > initial_mem =3D initial_mem >> increment_size << increment_size; > =20 > machine->ram_size =3D initial_mem; > + machine->maxram_size =3D initial_mem; > /* let's propagate the changed ram size into the global variable. = */ > ram_size =3D initial_mem; > } >=20 I even have a private patch for that already :) --=20 Thanks, David / dhildenb