- * For 386 only, ensure that pages are installed in the
- * kernel_pmap with VM_PROT_WRITE enabled. This avoids
- * code in pmap_enter that disallows a read-only mapping
- * in the kernel's pmap. (See ri-osc CR1387.)
- *
- * An entry in kernel_pmap is made only by the kernel or
- * a collocated server -- by definition (;-)), the requester
- * is trusted code. If it asked for read-only access,
- * it won't attempt a write. We don't have to enforce the
- * restriction. (Naturally, this assumes that any collocated
- * server will _not_ depend on trapping write accesses to pages
- * mapped read-only; this cannot be made to work in the current
- * i386-inspired pmap model.)
+ * XXX
+ * The kernel max VM address is limited to 0xFF3FFFFF for now because
+ * some data structures are explicitly allocated at 0xFF400000 without
+ * VM's knowledge (see osfmk/i386/locore.s for the allocation of PTmap and co.).
+ * We can't let VM allocate memory from there.