tests: benchmarks: latency_measure: fix potential div by zero
If the count is zero in the heap_malloc_free test, a div by zero would happen, so add a condition to handle this potential error. Signed-off-by: Chen Peng1 <peng1.chen@intel.com>
This commit is contained in:
parent
d39410a217
commit
47670d1ba6
1 changed files with 12 additions and 2 deletions
|
@ -47,8 +47,18 @@ void heap_malloc_free(void)
|
||||||
count++;
|
count++;
|
||||||
}
|
}
|
||||||
|
|
||||||
PRINT_STATS_AVG("Average time for heap malloc", sum_malloc, count);
|
/* if count is 0, it means that there is not enough memory heap
|
||||||
PRINT_STATS_AVG("Average time for heap free", sum_free, count);
|
* to do k_malloc at least once, then it's meaningless to
|
||||||
|
* calculate average time of memory allocation and free.
|
||||||
|
*/
|
||||||
|
if (count == 0) {
|
||||||
|
printk("Error: there isn't enough memory heap to do "
|
||||||
|
"k_malloc at least once, please "
|
||||||
|
"increase heap size\n");
|
||||||
|
} else {
|
||||||
|
PRINT_STATS_AVG("Average time for heap malloc", sum_malloc, count);
|
||||||
|
PRINT_STATS_AVG("Average time for heap free", sum_free, count);
|
||||||
|
}
|
||||||
|
|
||||||
timing_stop();
|
timing_stop();
|
||||||
}
|
}
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue