diff options
| author | Arnd Bergmann <[email protected]> | 2019-07-18 10:16:43 -0400 |
|---|---|---|
| committer | Mauro Carvalho Chehab <[email protected]> | 2019-07-23 11:42:20 -0400 |
| commit | 1a03f91c2c2419c3709c4554952c66695575e91c (patch) | |
| tree | d9016401feacfd10eb6004d55220d7bfeff059de /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 6732ecb335f5c8957ae319f50949b15f78d54621 (diff) | |
media: vivid: work around high stack usage with clang
Building a KASAN-enabled kernel with clang ends up in a case where too
much is inlined into vivid_thread_vid_cap() and the stack usage grows
a lot, possibly when the register allocation fails to produce efficient
code and spills a lot of temporaries to the stack. This uses more
than twice the amount of stack than the sum of the individual functions
when they are not inlined:
drivers/media/platform/vivid/vivid-kthread-cap.c:766:12: error: stack frame size of 2208 bytes in function 'vivid_thread_vid_cap' [-Werror,-Wframe-larger-than=]
Marking two of the key functions in here as 'noinline_for_stack' avoids
the pathological case in clang without any apparent downside for gcc.
Signed-off-by: Arnd Bergmann <[email protected]>
Acked-by: Nick Desaulniers <[email protected]>
Signed-off-by: Hans Verkuil <[email protected]>
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions