flexible-mmap breaks application
most at museresearch.com
Tue Mar 15 18:28:05 CST 2005
On Tue, 2005-03-15 at 15:55, Uwe Bonnes
> The definition of the task is clear:
> Have a way to tell the kernel to not mmap memory above 0x7fffffff
> However the implementation is unclear to me:
> - Should this be a new syscall?
> - Or should we set some kernel parameter? Per task or global?
There is a related problem in that Wine's VirtualAlloc won't allocate
the full 2GB it should. As I understand it the problem is the different
memory ranges that linux and windows allocate from --- the intersection
of the two platforms is only 1GB (not the 2GB it should be) from
0x4000,0000 to 0x8000,0000.
Could this patch also include a lower limit, letting linux mmap from
addresses in the same range that win32 does?
PS: the thread on this issue starts at
It also covers the issue of Wine's lack of mlock/munlock functionality.
More information about the wine-devel