diff options
| author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2015-12-28 13:23:00 +0300 |
|---|---|---|
| committer | Stephen Boyd <sboyd@codeaurora.org> | 2016-02-02 04:01:46 +0300 |
| commit | 176d11690ba2c8ad59f99734d692f19f451c408b (patch) | |
| tree | b2c077ce67c9946ccf87fed1ae1888761d2077bf /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 3a6e84545129913613dc1a97bbe8e4f2378696ee (diff) | |
| download | linux-176d11690ba2c8ad59f99734d692f19f451c408b.tar.xz | |
clk: move core->parents allocation to clk_register()
Currently, __clk_core_init() allows failure of the kcalloc() for the
core->parents. So, clk_fetch_parent_index() and __clk_init_parent()
also try to allocate core->parents in case it has not been allocated
yet. Scattering memory allocation here and there makes things
complicated.
Like other clk_core members, allocate core->parents in clk_register()
and let it fail in case of memory shortage. If we cannot allocate
such a small piece of memory, the system is already insane. There is
no point to postpone the memory allocation.
Also, allocate core->parents regardless of core->num_parents. We want
it even if core->num_parents == 1 because clk_fetch_parent_index()
might be called against the clk_core with a single parent.
If core->num_parents == 0, core->parents is set to ZERO_SIZE_PTR. It
is harmless because no access happens to core->parents in such a case.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Vladimir Zapolskiy <vz@mleia.com>
Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions
