The virtual memory should depend on physical memory in size, not in position.
That's why it's called mapping.
And i already had success with mapping 64k at address greater than 0x70000000
on machines with only 256MB Ram and 512MB swap...
So something else must be wrong.
A wild guess from me:
I'm not sure if i gathered the information right, but it seems at least to me
that the failing addresses are higher than the stack, so maybe there is a wrong
assumption about stack growing direction in the mmap code that checks if the
virtual address requested hits the stack area? (On ARM the stack is descending)
** Changed in: linux-ti-omap4 (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/697004
Title:
mmap for fixed address fails for higher addresses
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
