diff options
| author | David Hildenbrand <david@redhat.com> | 2024-12-19 15:41:06 +0100 |
|---|---|---|
| committer | David Hildenbrand <david@redhat.com> | 2024-12-21 15:59:59 +0100 |
| commit | 3c6fb557d295949bea291c3bf88ee9c83392e78c (patch) | |
| tree | e08619720c21c4c53b8447fbce45fd9464408946 /backends/vhost-user.c | |
| parent | 85489fc3652d0c4433c940f1a80a952e8cb5d3cb (diff) | |
| download | qemu-3c6fb557d295949bea291c3bf88ee9c83392e78c.zip qemu-3c6fb557d295949bea291c3bf88ee9c83392e78c.tar.gz qemu-3c6fb557d295949bea291c3bf88ee9c83392e78c.tar.bz2 | |
s390x/s390-virtio-ccw: move setting the maximum guest size from sclp to machine code
Nowadays, it feels more natural to have that code located in
s390_memory_init(), where we also have direct access to the machine
object.
While at it, use the actual RAM size, not the maximum RAM size which
cannot currently be reached without support for any memory devices.
Consequently update s390_pv_vm_try_disable_async() to rely on the RAM size
as well, to avoid temporary issues while we further rework that
handling.
set_memory_limit() is temporary, we'll merge it with
s390_set_memory_limit() next.
Message-ID: <20241219144115.2820241-6-david@redhat.com>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
Diffstat (limited to 'backends/vhost-user.c')
0 files changed, 0 insertions, 0 deletions