Provided to both Dom0 and DomUs. Signed-off-by: Roger Pau Monné <roger....@citrix.com> --- Cc: Andrew Cooper <andrew.coop...@citrix.com> Cc: George Dunlap <george.dun...@eu.citrix.com> Cc: Ian Jackson <ian.jack...@eu.citrix.com> Cc: Jan Beulich <jbeul...@suse.com> Cc: Julien Grall <julien.gr...@arm.com> Cc: Konrad Rzeszutek Wilk <konrad.w...@oracle.com> Cc: Stefano Stabellini <sstabell...@kernel.org> Cc: Tim Deegan <t...@xen.org> Cc: Wei Liu <wei.l...@citrix.com> --- docs/misc/pvh.markdown | 15 +++++++++++++++ 1 file changed, 15 insertions(+)
diff --git a/docs/misc/pvh.markdown b/docs/misc/pvh.markdown index e85fb15374..639401a887 100644 --- a/docs/misc/pvh.markdown +++ b/docs/misc/pvh.markdown @@ -92,3 +92,18 @@ event channels. Delivery of those interrupts can be configured in the same way as HVM guests, check xen/include/public/hvm/params.h and xen/include/public/hvm/hvm\_op.h for more information about available delivery methods. + +## MTRR ## + +### Unprivileged guests ### + +PVH guests are booted with the default MTRR type set to write-back and MTRR +enabled. This allows DomUs to start with a sane MTRR state. Note that this will +have to be revisited when pci-passthrough is added to PVH in order to set MMIO +regions as UC. + +### Hardware domain ### + +A PVH hardware domain is booted with the same MTRR state as the one found on +the host. This is done because the hardware domain memory map is already a +modified copy of the host memory map, so the same MTRR setup should work. -- 2.17.0 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
