Be explcit that all calls to pmap_activate() and pmap_deactivate()
from MI code are made with preemption disabled and with l == curlwp.

pmap_remove_all(): Return a boolean value to indicate the behaviour. If
true, all mappings have been removed, the pmap is totally cleared out, and
UVM can then avoid doing the work to call pmap_remove() for each map entry.
If false, either nothing has been done, or some helpful arch-specific voodoo
has taken place.

Remove Pp before It, where it has no effect.

add a note about pmap_activate() and pmap_deactivate() not being allow to block.

branches: 1.44.30; 1.44.32;
fix a description of PMAP_PREFER argument.

branches: 1.43.6;
Turn PMAP_NOCACHE into MI flag.
Add MI flags PMAP_WRITE_COMBINE, PMAP_WRITE_BACK, PMAP_NOCACHE_OVR.
Update pmap(9) manpage.

hppa: Remove MD PMAP_NOCACHE flag as it exists as MI flag
mips: Rename MD PMAP_NOCACHE to PGC_NOCACHE.

x86: Implement new MI flags using Page-Attribute Tables.
x86: Implement BUS_SPACE_MAP_PREFETCHABLE.

Patch presented on tech-kern@:
http://mail-index.netbsd.org/tech-kern/2010/06/30/msg008458.html

No comments on this last version.

branches: 1.42.2;
Use .In instead of .Aq Pa for header files.

Remove leading zero from Dd. New sentence, new line.

Update pmap(9) manpage:
- Document new flags argument for pmap_kenter_pa
- Document new flags argument for pmap_enter as well
- Document the prot argument for pmap_kenter_pa. This is copy&pasted from
pmap_enter.
Patch showed on tech-kern@ http://mail-index.netbsd.org/tech-kern/2009/11/04/msg006436.html
Thanks to Martin Husemann for his comments to the original patch version.

pmap(9): G/C pmap_collect, bump date.

play the "make signature match implementation-after-churn" game

pmap_kernel() is syntactic sugar for kernel_pmap_ptr now.

Convert TNF licenses to new 2 clause variant

branches: 1.35.4; 1.35.6;
pmap_phys_address: the prototype for this asks for a paddr_t, not an int.

branches: 1.34.2;
boolean_t -> bool

TRUE -> true, FALSE -> false.

Explicitly mention that pmap_extract() should deal with KSEG-style
kernel addresses.

Sync PMAP_PREFER(9) usage with -current implemetation.

Uppercase CPU. Remove a superfluous double quote. Use Dv for defined
values.

document pmap_procwr.

Grammar improvements.

document PMAP_PREFER. bump date.

s/the the/the/ (only in sources that aren't regularly imported from
elsewhere).

pmap_{de,}activate() take struct lwp * now

+ bump date!

Back out the following chagne:
http://mail-index.netbsd.org/source-changes/2003/05/08/0068.html

There were some side-effects that I didn't anticipate, and fixing them
is proving to be more difficult than I thought, do just eject for now.
Maybe one day we can look at this again.

Fixes PR kern/21517.

Simplify the way the bounds of the managed kernel virtual address
space is advertised to UVM by making virtual_avail and virtual_end
first-class exported variables by UVM. Machine-dependent code is
responsible for initializing them before main() is called. Anything
that steals KVA must adjust these variables accordingly.

This reduces the number of instances of this info from 3 to 1, and
Simplify the way the bounds of the managed kernel virtual address
space is advertised to UVM by making virtual_avail and virtual_end
first-class exported variables by UVM. Machine-dependent code is
responsible for initializing them before main() is called. Anything
that steals KVA must adjust these variables accordingly.

This reduces the number of instances of this info from 3 to 1, and
simplifies the pmap(9) interface by removing the pmap_virtual_space()
function call, and removing two arguments from pmap_steal_memory().

Simplify the way the bounds of the managed kernel virtual address
space is advertised to UVM by making virtual_avail and virtual_end
first-class exported variables by UVM. Machine-dependent code is
responsible for initializing them before main() is called. Anything
that steals KVA must adjust these variables accordingly.

This reduces the number of instances of this info from 3 to 1, and
simplifies the pmap(9) interface by removing the pmap_virtual_space()
function call, and removing two arguments from pmap_steal_memory().

This also eliminates some kludges such as having to burn kernel_map
entries on space used by the kernel and stolen KVA.

This also eliminates use of VM_{MIN,MAX}_KERNEL_ADDRESS from MI code,
this giving MD code greater flexibility over the bounds of the managed
kernel virtual address space if a given port's specific platforms can
vary in this regard (this is especially true of the evb* ports).

Use
.In header.h
instead of
.Fd #include \*[Lt]header.h\*[Gt]
Much easier to read and write, and supported by groff for ages.
Okayed by ross.

More e.g. cleanup. Igor Sobrado, PR 19692.

The correct capitalisation of 'NetBSD.org' is (you
guessed it) 'NetBSD.org'.

some mdoc fixes.

"Utilize" has exactly the same meaning as "use," but it is more
difficult to read and understand. Most manuals of English style
therefore say that you should use "use".

Bump date for pmap_remove addition.
Begin new sentences on new lines.
Use .Aq as much as possible instead of \*[Lt]foo\*[Gt].

document new stuff:
UVM_KMF_CANFAIL, uvm_uarea_alloc(), uvm_uarea_free(), pmap_remove_all().

Mdoc nits unrelated to last commit, and bump date for last commit.

* Document the existing requirement that machine-independent code
not pmap_kenter_pa() a mapping at a virtual address for which a
valid mapping already exists.
* Document the new requirement that machine-independent code not
not pmap_kenter_pa() a mapping with VM_PROT_EXEC.

branches: 1.14.2;
correct and clarify the previous revision.

Explicitly document previously undocumented (and changed) semantics
of pmap_clear_reference and pmap_clear_modify.

Generate <>& symbolically. I'm avoiding .../dist/... directories for now.

Edit -mdoc usage.

* There is no -indent option to .Bd or .Bl, although you would
never know that from its frequent use in this tree. There is a
"-offset indent" combination that makes sense, and you can certainly
say "-width indent".

* Also, you can't markup the -width option argument, tho you CAN
use a callable macro. So "-width Ar filename" doesn't make sense,
but either "-width Ar" or "-width filename" does, as might something
like "-width xxfilename" for a little extra space.

* There are a lot of needlessly complex hanging tag macros in man4 used
to create simple item lists. Those should be simplified one of these
days before someone copies and edits yet another man4 page.

Sort sections.

Use standard section headers.

Update man page with pmap_update change.

Boring whitespace fixes.

In the summary, fix pmap_steal_memory return type from void to vaddr_t.

vm_page_t -> struct vm_page *.

Tyop poleece.

Fix typo: maching -> machine

Minor punctuation corrections.

Add a manual page that describes the pmap(9) API and the requirements
of a pmap module.

Many thanks to Bill Sommerfeld for reviewing the document for me.