aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/lima/lima_sched.c
diff options
context:
space:
mode:
authorSteven Rostedt <[email protected]>2025-07-03 15:52:22 +0000
committerSteven Rostedt (Google) <[email protected]>2025-07-23 00:13:16 +0000
commit9b4d5d330fcd40bbc38a1e6ed3d617e674d651fa (patch)
tree22694211100e8f6ecc0ee8221ab2b2e4b1d2cc68 /drivers/gpu/drm/lima/lima_sched.c
parentfgraph: Keep track of when fgraph_ops are registered or not (diff)
downloadkernel-9b4d5d330fcd40bbc38a1e6ed3d617e674d651fa.tar.gz
kernel-9b4d5d330fcd40bbc38a1e6ed3d617e674d651fa.zip
ftrace: Make DYNAMIC_FTRACE always enabled for architectures that support it
ftrace has two flavors: 1) static: Where every function always calls the ftrace trampoline 2) dynamic: Where each function has nops that can be changed on demand to jump to the ftrace trampoline when needed. The static flavor has very high performance overhead and was only created to make it easier for architectures to implement the dynamic flavor. An architecture developer can first implement the static ftrace to make sure the trampolines work before working on the more complicated dynamic aspect of ftrace. Once the architecture can support dynamic ftrace, there's no reason to continue to support the static flavor. In fact, the static flavor tends to bitrot and bugs start to appear in them. Remove the prompt to pick DYNAMIC_FTRACE and simply enable it if the architecture supports it. Link: https://lore.kernel.org/all/[email protected]/ Cc: Masami Hiramatsu <[email protected]> Cc: Mathieu Desnoyers <[email protected]> Cc: Mark Rutland <[email protected]> Cc: Linus Torvalds <[email protected]> Cc: Alexandre Ghiti <[email protected]> Cc: ChenMiao <[email protected]> Link: https://lore.kernel.org/[email protected] Signed-off-by: Steven Rostedt (Google) <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/lima/lima_sched.c')
0 files changed, 0 insertions, 0 deletions