Re: [Qemu-devel] [PATCH for-4.2 v5 1/2] kvm: s390: split too big memory section on several memslots

On Thu, 29 Aug 2019 08:47:49 +0200 Christian Borntraeger wrote: > On 27.08.19 14:56, Igor Mammedov wrote: > > On Tue, 20 Aug 2019 18:07:27 +0200 > > Cornelia Huck wrote: > > > >> On Wed, 7 Aug 2019 11:32:41 -0400 > >> Igor Mammedov wrote: > >> > >>> Max memslot size supported by kvm on

Re: [Qemu-devel] [PATCH for-4.2 v5 1/2] kvm: s390: split too big memory section on several memslots

On 27.08.19 14:56, Igor Mammedov wrote: > On Tue, 20 Aug 2019 18:07:27 +0200 > Cornelia Huck wrote: > >> On Wed, 7 Aug 2019 11:32:41 -0400 >> Igor Mammedov wrote: >> >>> Max memslot size supported by kvm on s390 is 8Tb, >>> move logic of splitting RAM in chunks upto 8T to KVM code. >>> >>>

Re: [Qemu-devel] [PATCH for-4.2 v5 1/2] kvm: s390: split too big memory section on several memslots

On Tue, 20 Aug 2019 18:07:27 +0200 Cornelia Huck wrote: > On Wed, 7 Aug 2019 11:32:41 -0400 > Igor Mammedov wrote: > > > Max memslot size supported by kvm on s390 is 8Tb, > > move logic of splitting RAM in chunks upto 8T to KVM code. > > > > This way it will hide KVM specific restrictions in

Re: [Qemu-devel] [PATCH for-4.2 v5 1/2] kvm: s390: split too big memory section on several memslots

On Wed, 7 Aug 2019 11:32:41 -0400 Igor Mammedov wrote: > Max memslot size supported by kvm on s390 is 8Tb, > move logic of splitting RAM in chunks upto 8T to KVM code. > > This way it will hide KVM specific restrictions in KVM code > and won't affect baord level design decisions. Which would

[Qemu-devel] [PATCH for-4.2 v5 1/2] kvm: s390: split too big memory section on several memslots

Max memslot size supported by kvm on s390 is 8Tb, move logic of splitting RAM in chunks upto 8T to KVM code. This way it will hide KVM specific restrictions in KVM code and won't affect baord level design decisions. Which would allow us to avoid misusing memory_region_allocate_system_memory() API