perf ui progress: Make sure we always define step value

Unlikely, but we could have ui_progress__init being called with total <
16, which would set the next and step variables to 0. That would force
unnecessary ui_progress__ops->update calls because 'next' would never
raise.

Forcing the next and step values to be always > 0.

Signed-off-by: Jiri Olsa <jolsa@kernel.org>
Cc: David Ahern <dsahern@gmail.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Link: http://lkml.kernel.org/r/20170908120510.22515-2-jolsa@kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

authored by

Jiri Olsa and committed by
Arnaldo Carvalho de Melo
4d286c89 cd6379eb

+1 -1
+1 -1
tools/perf/ui/progress.c
··· 25 void ui_progress__init(struct ui_progress *p, u64 total, const char *title) 26 { 27 p->curr = 0; 28 - p->next = p->step = total / 16; 29 p->total = total; 30 p->title = title; 31
··· 25 void ui_progress__init(struct ui_progress *p, u64 total, const char *title) 26 { 27 p->curr = 0; 28 + p->next = p->step = total / 16 ?: 1; 29 p->total = total; 30 p->title = title; 31