[Xen-changelog] [xen staging] ARM/boot: Don't poison 'current' during early boot

[patchbot@xxxxxxx]

commit 1a42c2fcd29642ceaae9e5a12bb9c5c6f4b92813
Author:     Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
AuthorDate: Wed Jan 15 18:43:58 2020 +0000
Commit:     Julien Grall <julien@xxxxxxx>
CommitDate: Thu Jan 16 12:43:36 2020 +0000

    ARM/boot: Don't poison 'current' during early boot
    
    This logic was inherited from x86 (which was updated several times since).
    Unlike x86 (at the time) however, while NULL isn't mapped in ARM, 0xfffff000
    is, making this actively dangerous.
    
    Drop the logic entirely, and leave 'current' as NULL during early boot.
    
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Julien Grall <julien@xxxxxxx>
---
 xen/arch/arm/setup.c | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c
index 3c899cd4a0..9dd3738d44 100644
--- a/xen/arch/arm/setup.c
+++ b/xen/arch/arm/setup.c
@@ -798,9 +798,6 @@ void __init start_xen(unsigned long boot_phys_offset,
     percpu_init_areas();
     set_processor_id(0); /* needed early, for smp_processor_id() */
 
-    set_current((struct vcpu *)0xfffff000); /* debug sanity */
-    idle_vcpu[0] = current;
-
     setup_virtual_regions(NULL, NULL);
     /* Initialize traps early allow us to get backtrace when an error occurred 
*/
     init_traps();
--
generated by git-patchbot for /home/xen/git/xen.git#staging

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