While checking xen dom0less documentation it has been found
that domU memory property requires extra 0x0 in case of arm64.
There is no need to keep memory size in u64, 32 bits is
enough for domU memory size.
Tested that in case of arm64 dom0less domU works
without adding extra 0x0 to domU memory property with this patch.
Signed-off-by: Viktor Mitin <viktor_mi...@epam.com>
---
xen/arch/arm/domain_build.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
index d9836779d1..2c1a8c243e 100644
--- a/xen/arch/arm/domain_build.c
+++ b/xen/arch/arm/domain_build.c
@@ -2012,9 +2012,9 @@ static int __init construct_domU(struct domain *d,
{
struct kernel_info kinfo = {};
int rc;
- u64 mem;
+ u32 mem;
- rc = dt_property_read_u64(node, "memory", &mem);
+ rc = dt_property_read_u32(node, "memory", &mem);
if ( !rc )
{
printk("Error building DomU: cannot read \"memory\" property\n");
@@ -2022,7 +2022,7 @@ static int __init construct_domU(struct domain *d,
}
kinfo.unassigned_mem = (paddr_t)mem * SZ_1K;
- printk("*** LOADING DOMU cpus=%u memory=%"PRIx64"KB ***\n", d->max_vcpus,
mem);
+ printk("*** LOADING DOMU cpus=%u memory=%"PRIx32"KB ***\n", d->max_vcpus,
mem);
kinfo.vpl011 = dt_property_read_bool(node, "vpl011");
--
2.17.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
