On 08/15/2018 10:15 AM, Omkar Bolla wrote:
HI Julien,
Hello,
As you suggested, I enabled early printk for hikey960 in xen-4.8 stable
branch and xen-4.11 stable branch.
Looking at the logs, Xen is placed differently in the memory:
- Xen 4.8: 0x000000001aa00000
- Xen 4.11: 0x000000021fe00000
With Xen 4.11, the binary will be placed above 4GB. There was some
change in the way to place Xen in the memory in 2016 allowing to place
Xen at the end of the usable RAM.
I suspect the firmware does not support 64-bit address entry point for
secondary CPU. This would explain the ADDRESS_INVALID from PSCI CPU UP
call. Can you give a try to this patch:
diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c
index 7d40a8466b..13318da6b1 100644
--- a/xen/arch/arm/setup.c
+++ b/xen/arch/arm/setup.c
@@ -408,13 +408,11 @@ static paddr_t __init get_xen_paddr(void)
if ( !e )
continue;
-#ifdef CONFIG_ARM_32
/* Xen must be under 4GB */
if ( e > 0x100000000ULL )
e = 0x100000000ULL;
if ( e < bank->start )
continue;
-#endif
s = e - min_size;
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel