Jason R Thorpe <thorpej@netbsd.org> writes:

> 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).

Since kernel_map no longer cover the region below the virtual_start,
uvm_kernacc() returns false for the access to such region.

enami.