[Xen-changelog] [xen staging] xen/arm32: mm: Avoid to zero and clean cache for CPU0 domheap

[patchbot@xxxxxxx]

commit 4bfb26e419b73c28a935cce14ac3a63be9f3c1ba
Author:     Julien Grall <julien.grall@xxxxxxx>
AuthorDate: Sun Apr 7 20:59:22 2019 +0100
Commit:     Julien Grall <julien.grall@xxxxxxx>
CommitDate: Thu Jun 6 18:44:33 2019 +0100

    xen/arm32: mm: Avoid to zero and clean cache for CPU0 domheap
    
    The page-table walker is configured to use the same shareability and
    cacheability as the access performed when updating the page-tables. This
    means cleaning the cache for CPU0 domheap is unnecessary.
    
    Furthermore, CPU0 page-tables are part of Xen binary and will already be
    zeroed before been used. So it is pointless to zero the domheap again.
    
    Signed-off-by: Julien Grall <julien.grall@xxxxxxx>
    Reviewed-by: Andrii Anisov <andrii_anisov@xxxxxxxx>
    Reviewed-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>
---
 xen/arch/arm/mm.c | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/xen/arch/arm/mm.c b/xen/arch/arm/mm.c
index bd1942f7f1..ee72fb5e8f 100644
--- a/xen/arch/arm/mm.c
+++ b/xen/arch/arm/mm.c
@@ -696,11 +696,6 @@ void __init setup_pagetables(unsigned long 
boot_phys_offset)
 #ifdef CONFIG_ARM_32
     per_cpu(xen_pgtable, 0) = cpu0_pgtable;
     per_cpu(xen_dommap, 0) = cpu0_dommap;
-
-    /* Make sure it is clear */
-    memset(this_cpu(xen_dommap), 0, DOMHEAP_SECOND_PAGES*PAGE_SIZE);
-    clean_dcache_va_range(this_cpu(xen_dommap),
-                              DOMHEAP_SECOND_PAGES*PAGE_SIZE);
 #endif
 }
 
--
generated by git-patchbot for /home/xen/git/xen.git#staging

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/xen-changelog