Re: paddr_t change to 64-bits

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Tue, 28 Sep 2010 01:51:04 +0200
    From:        Jean-Yves Migeon <jeanyves.migeon%free.fr@localhost>
    Message-ID:  <4CA12DE8.1080706%free.fr@localhost>

  | Using paddr_t is unfortunate there:

It isn't "unfortunate", it's wrong, if paddr_t isn't going to remain a
constant type for the life of an API (that is, if just switching kernel
options can change it) then it must be kept completely out of the API
(ie: nothing, with the possible exception of libkvm, which can almost be
considered a kernel adjunct) can be allowed to use it for anything.

If its usage is already too embedded for that to be possible, then paddr_t
needs to become a "fixed" type, and something else needs to be created to be
be used as the data type for addresses shose size varies depending upon
the whim of whoever booted the most recent kernel.

kre