--OaZoDhBhXzo6bW1J
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

I'd like to specify that exec mappings are not allowed to be entered
via pmap_kenter_pa() (at least, not by machine-independent code).  I'm
pretty sure no MI code does this as it stands.

Attached is text for the pmap(9) manual page.  Comments?

-- 
        -- Jason R. Thorpe <thorpej@wasabisystems.com>

--OaZoDhBhXzo6bW1J
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="pmap.9-diff"

Index: pmap.9
===================================================================
RCS file: /cvsroot/sharesrc/share/man/man9/pmap.9,v
retrieving revision 1.14
diff -c -r1.14 pmap.9
*** pmap.9	2002/04/01 17:30:02	1.14
--- pmap.9	2002/08/09 22:58:05
***************
*** 288,295 ****
  (for example, the kernel memory allocator), or to enter mappings for
  physical addresses which are not managed by the virtual memory system.
  .Dq Unmanaged
! mappings may only be entered into the kernel's virtual address space.
! This constraint is placed on the callers of the
  .Fn pmap_kenter_pa
  and
  .Fn pmap_kremove
--- 288,298 ----
  (for example, the kernel memory allocator), or to enter mappings for
  physical addresses which are not managed by the virtual memory system.
  .Dq Unmanaged
! mappings may only be entered into the kernel's virtual address space.  In
! addition, no mappings should be entered by machine-independent code with
! executable permission should be entered via
! .Fn pmap_kenter_pa .
! These constraints are placed on the callers of the
  .Fn pmap_kenter_pa
  and
  .Fn pmap_kremove

--OaZoDhBhXzo6bW1J--