[Xen-devel] [PATCH] x86: fix comment on super page alignment requirement

[Wei Liu <wei.liu2@xxxxxxxxxx>]

BOOTSTRAP_DIRECTMAP_END is gone. The comment in question should refer
to BOOSTRAP_MAP_BASE and BOOTSTRAP_MAP_LIMIT instead.

Remove two trailing spaces while fixing the comment.

Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
---
 xen/arch/x86/setup.c | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/xen/arch/x86/setup.c b/xen/arch/x86/setup.c
index fb2a194119..958dca9fc5 100644
--- a/xen/arch/x86/setup.c
+++ b/xen/arch/x86/setup.c
@@ -944,12 +944,13 @@ void __init noreturn __start_xen(unsigned long mbi_p)
 
     /*
      * Iterate backwards over all superpage-aligned RAM regions.
-     * 
-     * We require superpage alignment because the boot allocator is not yet
-     * initialised. Hence we can only map superpages in the address range
-     * 0 to BOOTSTRAP_DIRECTMAP_END, as this is guaranteed not to require
+     *
+     * We require superpage alignment because the boot allocator is
+     * not yet initialised. Hence we can only map superpages in the
+     * address range BOOTSTRAP_MAP_BASE to (BOOTSTRAP_MAP_BASE +
+     * BOOTSTRAP_MAP_LIMIT), as this is guaranteed not to require
      * dynamic allocation of pagetables.
-     * 
+     *
      * As well as mapping superpages in that range, in preparation for
      * initialising the boot allocator, we also look for a region to which
      * we can relocate the dom0 kernel and other multiboot modules. Also, on
-- 
2.11.0


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel