summaryrefslogtreecommitdiffstats
path: root/sys/i386
diff options
context:
space:
mode:
authordyson <dyson@FreeBSD.org>1996-12-30 05:31:21 +0000
committerdyson <dyson@FreeBSD.org>1996-12-30 05:31:21 +0000
commitc232302d3fb7bc2db6053e608cf8843199fea7c1 (patch)
tree897f659fee68ca11a992ee3be71d600f4e9207dc /sys/i386
parenta61ba0575d63937c042107bda370e8c8590d6120 (diff)
downloadFreeBSD-src-c232302d3fb7bc2db6053e608cf8843199fea7c1.zip
FreeBSD-src-c232302d3fb7bc2db6053e608cf8843199fea7c1.tar.gz
Let the VM system know that on certain arch's that VM_PROT_READ
also implies VM_PROT_EXEC. We support it that way for now, since the break system call by default gives VM_PROT_ALL. Now we have a better chance of coalesing map entries when mixing mmap/break type operations. This was contributing to excessive numbers of map entries on the modula-3 runtime system. The problem is still not "solved", but the situation makes more sense. Eventually, when we work on architectures where VM_PROT_READ is orthogonal to VM_PROT_EXEC, we will have to visit this issue carefully (esp. regarding security issues.)
Diffstat (limited to 'sys/i386')
-rw-r--r--sys/i386/include/vmparam.h4
1 files changed, 3 insertions, 1 deletions
diff --git a/sys/i386/include/vmparam.h b/sys/i386/include/vmparam.h
index 48b570d..5c3774e 100644
--- a/sys/i386/include/vmparam.h
+++ b/sys/i386/include/vmparam.h
@@ -36,7 +36,7 @@
* SUCH DAMAGE.
*
* from: @(#)vmparam.h 5.9 (Berkeley) 5/12/91
- * $Id: vmparam.h,v 1.20 1996/04/30 12:02:12 phk Exp $
+ * $Id: vmparam.h,v 1.21 1996/05/02 14:20:07 phk Exp $
*/
@@ -47,6 +47,8 @@
* Machine dependent constants for 386.
*/
+#define VM_PROT_READ_IS_EXEC /* if you can read -- then you can exec */
+
/*
* Virtual memory related constants, all in bytes
*/
OpenPOWER on IntegriCloud