From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55352) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ePTSR-00065c-An for qemu-devel@nongnu.org; Thu, 14 Dec 2017 08:21:52 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ePTSO-0004s7-5G for qemu-devel@nongnu.org; Thu, 14 Dec 2017 08:21:51 -0500 Date: Thu, 14 Dec 2017 14:21:38 +0100 From: Cornelia Huck Message-ID: <20171214142138.3a5c9eef.cohuck@redhat.com> In-Reply-To: <20171211122146.162430-1-borntraeger@de.ibm.com> References: <20171211122146.162430-1-borntraeger@de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3 1/1] s390-ccw-virtio: allow for systems larger that 7.999TB List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Christian Borntraeger Cc: qemu-devel , qemu-s390x , Halil Pasic , Alexander Graf , Thomas Huth , David Hildenbrand , Richard Henderson On Mon, 11 Dec 2017 13:21:46 +0100 Christian Borntraeger wrote: > KVM does not allow memory regions > KVM_MEM_MAX_NR_PAGES, basically > limiting the memory per slot to 8TB-4k. As memory slots on s390/kvm must > be a multiple of 1MB we need start a new memory region if we cross > 8TB-1M. > > With that (and optimistic overcommitment in the kernel) I was able to > start a 24TB guest on a 1TB system. > > Signed-off-by: Christian Borntraeger > --- > hw/s390x/s390-virtio-ccw.c | 28 +++++++++++++++++++++++++--- > 1 file changed, 25 insertions(+), 3 deletions(-) Thanks, applied (with 1UL -> 1ULL).