Re: pmap_extract(9) (was Re: xmd(4) (Re: XIP))

[Matt Thomas <matt%3am-software.com@localhost>]

On Nov 1, 2010, at 8:55 AM, Eduardo Horvath wrote:

> On Mon, 1 Nov 2010, Masao Uebayashi wrote:
> 
>> I think pmap_extract(9) is a bad API.
>> 
>> After MD bootstrap code detects all physical memories, it gives
>> all the informations to UVM, including available KVA.  At this
>> point UVM knows all the available resources of virtual/physical
>> addresses.  UVM is responsible to manage all of these.
> 
> This is managed RAM.  What about I/O pages?

Indeed.  Also consider that pmap's are designed to have to have
fast V->P translations, using that instead of UVM makes a lot of
sense.