diff options
author | David Hildenbrand <david@redhat.com> | 2018-06-28 13:38:16 +0200 |
---|---|---|
committer | Cornelia Huck <cohuck@redhat.com> | 2018-07-02 10:37:38 +0200 |
commit | 8151942151fe1cbf072414d8822b80b00abfbf42 (patch) | |
tree | a0286ea68e01c91d0ff97d5a6d62bab55a83118f /include/hw/loader.h | |
parent | d66b43c896f89d610f8738169db8e10e63a3a9e6 (diff) | |
download | qemu-8151942151fe1cbf072414d8822b80b00abfbf42.zip qemu-8151942151fe1cbf072414d8822b80b00abfbf42.tar.gz qemu-8151942151fe1cbf072414d8822b80b00abfbf42.tar.bz2 |
s390x/kvm: legacy_s390_alloc() only supports one allocation
We always allocate at a fixed address, a second allocation can therefore
of course never work. We would simply overwrite mappings.
This can e.g. happen in s390_memory_init(), if trying to allocate more
than > 8TB. Let's just bail out, as there is no need for supporting it
(legacy handling for z/VM).
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20180628113817.30814-2-david@redhat.com>
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
Diffstat (limited to 'include/hw/loader.h')
0 files changed, 0 insertions, 0 deletions