| commit | 50a17297e2f0c4d621c7bb23fee239c0a3fd3128 | |
| author | Eric Auger <eric.auger@redhat.com> | |
| Mon, 4 Mar 2019 10:13:39 +0000 (4 11:13 +0100) | ||
| committer | Peter Maydell <peter.maydell@linaro.org> | |
| Tue, 5 Mar 2019 15:55:09 +0000 (5 15:55 +0000) | ||
| tree | 6b9fd0f22c6ca488b815cc584e0a314f12c719ba | treesnapshot (tar.gz zip) |
| parent | 2ba956ccfa718c68ae95356fe5e7de6208cf97f0 | commitdiff |
hw/arm/virt: Bump the 255GB initial RAM limit
Now we have the extended memory map (high IO regions beyond the
scalable RAM) and dynamic IPA range support at KVM/ARM level
we can bump the legacy 255GB initial RAM limit. The actual maximum
RAM size now depends on the physical CPU and host kernel, in
accelerated mode. In TCG mode, it depends on the VCPU
AA64MMFR0.PARANGE.
Signed-off-by: Eric Auger <eric.auger@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Message-id: 20190304101339.25970-11-eric.auger@redhat.com
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Now we have the extended memory map (high IO regions beyond the
scalable RAM) and dynamic IPA range support at KVM/ARM level
we can bump the legacy 255GB initial RAM limit. The actual maximum
RAM size now depends on the physical CPU and host kernel, in
accelerated mode. In TCG mode, it depends on the VCPU
AA64MMFR0.PARANGE.
Signed-off-by: Eric Auger <eric.auger@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Message-id: 20190304101339.25970-11-eric.auger@redhat.com
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
| hw/arm/virt.c | diffblobblamehistory |