| commit | 5e6aa26723f3eb67016282709fda7835a975f1ab | |
| author | David Hildenbrand <david@redhat.com> | |
| Tue, 23 Oct 2018 15:23:05 +0000 (23 17:23 +0200) | ||
| committer | Eduardo Habkost <ehabkost@redhat.com> | |
| Tue, 11 Dec 2018 17:45:22 +0000 (11 15:45 -0200) | ||
| tree | 46e6c6f677b9758b2f297d3904fad7e61cc0be72 | treesnapshot (tar.gz zip) |
| parent | 3e18dbbb13a476072b98ff3250d4558b446fa7b8 | commitdiff |
memory-device: avoid overflows on very huge devices
Should not be a problem right now, but it could theoretically happen
in the future.
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20181023152306.3123-7-david@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Should not be a problem right now, but it could theoretically happen
in the future.
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20181023152306.3123-7-david@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
| hw/mem/memory-device.c | diffblobblamehistory |