>>> On 10.05.17 at 13:13, <igor.druzhi...@citrix.com> wrote: > The same set of functions is used to set as well as to clean > P2M entries, except that for clean operations INVALID_MFN (~0UL) > is passed as a parameter. Unfortunately, when calculating an > appropriate target order for a particular mapping INVALID_MFN > is not taken into account which leads to 4K page target order > being set each time even for 2MB and 1GB mappings. This eventually > breaks down an EPT structure irreversibly into 4K mappings which > prevents consecutive high order mappings to this area. > > Signed-off-by: Igor Druzhinin <igor.druzhi...@citrix.com>
Reviewed-by: Jan Beulich <jbeul...@suse.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
