Commit c638ebd
committed
ftrace: Do not bother checking per CPU "disabled" flag
The per CPU "disabled" value was the original way to disable tracing when
the tracing subsystem was first created. Today, the ring buffer
infrastructure has its own way to disable tracing. In fact, things have
changed so much since 2008 that many things ignore the disable flag.
There's no reason for the function tracer to check it, if tracing is
disabled, the ring buffer will not record the event anyway.
Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Link: https://lore.kernel.org/20250505212234.868972758@goodmis.org
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>1 parent 6936298 commit c638ebd
1 file changed
Lines changed: 3 additions & 13 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
209 | 209 | | |
210 | 210 | | |
211 | 211 | | |
212 | | - | |
213 | 212 | | |
214 | 213 | | |
215 | 214 | | |
| |||
224 | 223 | | |
225 | 224 | | |
226 | 225 | | |
227 | | - | |
228 | | - | |
229 | | - | |
| 226 | + | |
230 | 227 | | |
231 | 228 | | |
232 | 229 | | |
| |||
236 | 233 | | |
237 | 234 | | |
238 | 235 | | |
239 | | - | |
240 | 236 | | |
241 | 237 | | |
242 | | - | |
243 | 238 | | |
244 | 239 | | |
245 | 240 | | |
| |||
250 | 245 | | |
251 | 246 | | |
252 | 247 | | |
253 | | - | |
254 | | - | |
255 | | - | |
256 | | - | |
| 248 | + | |
257 | 249 | | |
258 | 250 | | |
259 | 251 | | |
| |||
352 | 344 | | |
353 | 345 | | |
354 | 346 | | |
355 | | - | |
356 | 347 | | |
357 | 348 | | |
358 | 349 | | |
| |||
364 | 355 | | |
365 | 356 | | |
366 | 357 | | |
367 | | - | |
368 | | - | |
| 358 | + | |
369 | 359 | | |
370 | 360 | | |
371 | 361 | | |
| |||
0 commit comments