Alan Cox beb3c3a9c5 Retire VM_PROT_READ_IS_EXEC. It was intended to be a micro-optimization, ... but I see no benefit from it today. VM_PROT_READ_IS_EXEC was only intended for use on processors that do not distinguish between read and execute permission. On an mmap(2) or mprotect(2), it automatically added execute permission if the caller specified permissions included read permission. The hope was that this would reduce the number of vm map entries needed to implement an address space because there would be fewer neighboring vm map entries that differed only in the presence or absence of VM_PROT_EXECUTE. (See vm/vm_mmap.c revision 1.56.) Today, I don't see any real applications that benefit from VM_PROT_READ_IS_EXEC. In any case, vm map entries are now organized as a self-adjusting binary search tree instead of an ordered list. So, the need for coalescing vm map entries is not as great as it once was.		2009-04-04 23:12:14 +00:00
..
arm	Use Oxf0000000 instead of 0xff000000 to guess the physical address, relative	2009-03-31 23:06:20 +00:00
at91
compile
conf	revert unintended change	2009-03-30 21:54:39 +00:00
include	Retire VM_PROT_READ_IS_EXEC. It was intended to be a micro-optimization,	2009-04-04 23:12:14 +00:00
mv
sa11x0
xscale