[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v3 02/13] iommu: introduce the concept of BFN...

On Tue, Jul 17, 2018 at 02:38:05PM +0100, Paul Durrant wrote:
> ...meaning 'bus frame number' i.e. a frame number mapped in the IOMMU
> rather than the MMU.
> This patch is a largely cosmetic change that substitutes the terms 'gfn'
> and 'gaddr' for 'bfn' and 'baddr' in all the places where the frame number
> or address relate to the IOMMU rather than the MMU.
> The parts that are not purely cosmetic are:
>  - the introduction of a type-safe declaration of bfn_t and definition of
>    INVALID_BFN to make the substitution of gfn_x(INVALID_GFN) mechanical.
>  - the introduction of __bfn_to_baddr and __baddr_to_bfn (and type-safe
>    variants without the leading __) with some use of the former.
> Subsequent patches will convert code to make use of type-safe BFNs.
> Signed-off-by: Paul Durrant <paul.durrant@xxxxxxxxxx>

Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx>

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.