diff options
| author | Igor Mammedov <imammedo@redhat.com> | 2019-09-24 10:47:50 -0400 |
|---|---|---|
| committer | Christian Borntraeger <borntraeger@de.ibm.com> | 2019-09-30 13:51:50 +0200 |
| commit | 023ae9a88a7cfbdf6f23c3b78ccfcb9b1e26da98 (patch) | |
| tree | a6cce4fc2cf06cabb13b4fa7cd1ba38d30e158a6 /hw/s390x | |
| parent | 84516e5b8db66b8a169a8fdd4c25568ed0b67a3a (diff) | |
| download | qemu-023ae9a88a7cfbdf6f23c3b78ccfcb9b1e26da98.zip qemu-023ae9a88a7cfbdf6f23c3b78ccfcb9b1e26da98.tar.gz qemu-023ae9a88a7cfbdf6f23c3b78ccfcb9b1e26da98.tar.bz2 | |
kvm: 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 board level design decisions. Which would allow
us to avoid misusing memory_region_allocate_system_memory() API
and eventually use a single hostmem backend for guest RAM.
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Message-Id: <20190924144751.24149-4-imammedo@redhat.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Diffstat (limited to 'hw/s390x')
0 files changed, 0 insertions, 0 deletions