aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/lima/lima_gem.c
diff options
context:
space:
mode:
authorSteven Rostedt <[email protected]>2025-07-04 14:48:38 +0000
committerSteven Rostedt (Google) <[email protected]>2025-07-23 00:15:56 +0000
commit4d6d0a6263babf7c43faa55de4fa3c6637dec624 (patch)
tree17c2a7509f4ddd4c9844a65750bb44b899a2b6c7 /drivers/gpu/drm/lima/lima_gem.c
parentftrace: Make DYNAMIC_FTRACE always enabled for architectures that support it (diff)
downloadkernel-4d6d0a6263babf7c43faa55de4fa3c6637dec624.tar.gz
kernel-4d6d0a6263babf7c43faa55de4fa3c6637dec624.zip
tracing: Remove redundant config HAVE_FTRACE_MCOUNT_RECORD
Ftrace is tightly coupled with architecture specific code because it requires the use of trampolines written in assembly. This means that when a new feature or optimization is made, it must be done for all architectures. To simplify the approach, CONFIG_HAVE_FTRACE_* configs are added to denote which architecture has the new enhancement so that other architectures can still function until they too have been updated. The CONFIG_HAVE_FTRACE_MCOUNT was added to help simplify the DYNAMIC_FTRACE work, but now every architecture that implements DYNAMIC_FTRACE also has HAVE_FTRACE_MCOUNT set too, making it redundant with the HAVE_DYNAMIC_FTRACE. Remove the HAVE_FTRACE_MCOUNT config and use DYNAMIC_FTRACE directly where applicable. 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]> Link: https://lore.kernel.org/[email protected] Signed-off-by: Steven Rostedt (Google) <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/lima/lima_gem.c')
0 files changed, 0 insertions, 0 deletions