That makes sense. Reading the man page myself, it does seem like:
-If the drivers can guarantee they set MAP_SHARED when creating their
initial mapping.
-If WINE is fine rounding down to page boundaries to deal with mappings
of suballocations and either using some lookup structure to avoid
d
I haven't read through the whole mail thread, but if you manage the
address space using mmap() then you always run into this issue.
If you manage the whole 4GiB address space by Wine then you never run
into this issue. You would just allocate some address range internally
and mremap() into tha
On 10/22/24 18:03, Derek Lesho wrote:
Am 10/21/24 um 11:35 schrieb Michel Dänzer:
And Wine's solution for this can't be implemented in Mesa?
I think this might actually be possible: In order to accomplish this
Wine essentially keeps calling mmaps with addresses in its range until
it finds
