tree 61f12110f71ea4430e0fa46bce6c25e113a8ad96
parent 4b0a32e57d3f9a3325d49cdcd1a0d20e6ab95dd6
author Andrew Scull <ascull@google.com> 1533553449 +0100
committer Andrew Scull <ascull@google.com> 1533835583 +0000

Better use of address types in mm.h.

These functions are called to map physical pages in and out of the
address space. It makes more sense for the APIs to use those physical
addresses and avoid mistakes or confusion in the conversions.

Once the physical address has been mapped it will be available as a
virtual address or pointer in the hypervisor and an intermediate
physical address in the VMs. The corresponding type is now returned from
the mapping functions to avoid complication or mistakes in conversion by
the caller and the vast majority of the address type conversions now
happen within mm.

Internally to mm, the stage 1 and stage 2 tables still share the same
management code so that is made generic for the type of input address
being used.

Change-Id: I9201b98b7329ead304903b8b8968c4378eb5a4db