| commit | 286690e34ce04fa29bf812ef2bb7b32c3e7c3b85 | |
| author | Paolo Bonzini <pbonzini@redhat.com> | |
| Wed, 6 Nov 2013 18:18:08 +0000 (6 20:18 +0200) | ||
| committer | Michael S. Tsirkin <mst@redhat.com> | |
| Tue, 10 Dec 2013 10:29:56 +0000 (10 12:29 +0200) | ||
| tree | be09c36a1ac8a756eed020676c296d2722aca901 | treesnapshot (tar.gz zip) |
| parent | cf252e5173e46aa4956b88a95fd09ef7eb38b8a6 | commitdiff |
pc: s/INT64_MAX/UINT64_MAX/
It doesn't make sense for a region to be INT64_MAX in size:
memory core uses UINT64_MAX as a special value meaning
"all 64 bit" this is what was meant here.
While this should never affect the PC system which at the moment always
has < 63 bit size, this makes us hit all kind of corner case bugs with
sub-pages, so users are probably better off if we just use UINT64_MAX
instead.
Reported-by: Luiz Capitulino <lcapitulino@redhat.com>
Tested-by: Luiz Capitulino <lcapitulino@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
It doesn't make sense for a region to be INT64_MAX in size:
memory core uses UINT64_MAX as a special value meaning
"all 64 bit" this is what was meant here.
While this should never affect the PC system which at the moment always
has < 63 bit size, this makes us hit all kind of corner case bugs with
sub-pages, so users are probably better off if we just use UINT64_MAX
instead.
Reported-by: Luiz Capitulino <lcapitulino@redhat.com>
Tested-by: Luiz Capitulino <lcapitulino@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
| hw/i386/pc_piix.c | diffblobblamehistory | |
| hw/i386/pc_q35.c | diffblobblamehistory |