Re: ASSERT in rangeset_remove_range

2021-11-09 Thread Stefano Stabellini
nd_unallocated_memory 994 s=2 e=1 > > (XEN) Assertion 's <= e' failed at rangeset.c:189 > > > > > > When a bank of memory is zero in size, then rangeset_remove_range is > > called with end < start, triggering an ASSERT in rangeset_remove_

Re: ASSERT in rangeset_remove_range

2021-11-09 Thread Jan Beulich
at rangeset.c:189 >> >> >> When a bank of memory is zero in size, then rangeset_remove_range is >> called with end < start, triggering an ASSERT in rangeset_remove_range. >> >> One solution is to avoid creating 0 size banks. The following change >> does that: >

Re: ASSERT in rangeset_remove_range

2021-11-09 Thread Julien Grall
in size, then rangeset_remove_range is called with end < start, triggering an ASSERT in rangeset_remove_range. One solution is to avoid creating 0 size banks. The following change does that: diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c index 49b4eb2b13..3efe542d0f 100644 --

Re: ASSERT in rangeset_remove_range

2021-11-09 Thread Oleksandr Tyshchenko
t;= e' failed at rangeset.c:189 > > > When a bank of memory is zero in size, then rangeset_remove_range is > called with end < start, triggering an ASSERT in rangeset_remove_range. > > One solution is to avoid creating 0 size banks. The following change > does that: >

ASSERT in rangeset_remove_range

2021-11-08 Thread Stefano Stabellini
find_unallocated_memory 994 s=4000 e=7e7f (XEN) DEBUG find_unallocated_memory 994 s=2 e=1 (XEN) Assertion 's <= e' failed at rangeset.c:189 When a bank of memory is zero in size, then rangeset_remove_range is called with end < start, triggering an ASSERT in rangeset_remove_rang