Il 20/06/2013 16:43, Peter Maydell ha scritto:
>>> >> There are other places in memory.c which do an int128_get64()
>>> >> on mr->size, which also look suspicious...
>> >
>> > They are all on I/O regions so they are safe
> Not entirely sure I understand this. There's no particular
> reason I can't create a 2^64 sized I/O memory region
> and put it in an address space, is there?
I think there are problems in the core if you do that (probably part of
it is fixed now). Still, in cases like this:
memory_region_add_coalescing(mr, 0, int128_get64(mr->size));
the API simply doesn't support it.
Paolo
