Lines Matching full:format

16 Generic PT is structured as a multi-compilation system. Since each format
17 provides an API using a common set of names there can be only one format active
22 map/unmap, etc.) and the per-format code can be directly inlined into the
23 per-format compilation unit. For something like IOMMU each format will be
24 compiled into a per-format IOMMU operations kernel module.
27 format headers and the generic code for the implementation. For instance in an
46 IOMMU implementation uses multi-compilation to generate per-format ops structs
49 The format code is written so that the common names arise from #defines to
50 distinct format specific names. This is intended to aid debuggability by
53 Exported symbols and other global names are mangled using a per-format string
56 The format uses struct pt_common as the top-level struct for the table,
57 and each format will have its own struct pt_xxx which embeds it to store
58 format-specific information.
63 Format functions at the struct pt_common level
75 Writing a Format
78 It is best to start from a simple format that is similar to the target. x86_64
82 The required inline functions need to be implemented in the format header.
91 where a uniquely named per-format inline function provides the implementation
99 Once the format compiles then it should be run through the generic page table
107 The generic tests are intended to prove out the format functions and give