initcall: Correct use of relocation offset
The relocation offset can change in some initcall sequences. Handle this and make sure it is used for all debugging statements in init_run_list() Update the trace test to match. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Caleb Connolly <caleb.connolly@linaro.org>
This commit is contained in:
@@ -175,7 +175,7 @@ def check_funcgraph(cons, fname, proftool, map_fname, trace_dat):
|
||||
# Then look for this:
|
||||
# u-boot-1 0..... 282.101375: funcgraph_exit: 0.006 us | }
|
||||
# Then check for this:
|
||||
# u-boot-1 0..... 282.101375: funcgraph_entry: 0.000 us | initcall_is_event();
|
||||
# u-boot-1 0..... 282.101375: funcgraph_entry: 0.000 us | calc_reloc_ofs();
|
||||
|
||||
expected_indent = None
|
||||
found_start = False
|
||||
@@ -199,7 +199,7 @@ def check_funcgraph(cons, fname, proftool, map_fname, trace_dat):
|
||||
|
||||
# The next function after initf_bootstage() exits should be
|
||||
# initcall_is_event()
|
||||
assert upto == 'initcall_is_event()'
|
||||
assert upto == 'calc_reloc_ofs()'
|
||||
|
||||
# Now look for initf_dm() and dm_timer_init() so we can check the bootstage
|
||||
# time
|
||||
|
||||
Reference in New Issue
Block a user