mirror of
https://github.com/torvalds/linux.git
synced 2026-05-30 10:04:04 +02:00
tracing: Do not use per CPU array_buffer.data->disabled for cpumask
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. Do not bother setting the per CPU disabled flag of the array_buffer data to use to determine what CPUs can write to the buffer and only rely on the ring buffer code itself to disabled it. 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/20250505212235.885452497@goodmis.org Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
This commit is contained in:
parent
f62e3de375
commit
969043af15
|
|
@ -5081,7 +5081,6 @@ int tracing_set_cpumask(struct trace_array *tr,
|
|||
*/
|
||||
if (cpumask_test_cpu(cpu, tr->tracing_cpumask) &&
|
||||
!cpumask_test_cpu(cpu, tracing_cpumask_new)) {
|
||||
atomic_inc(&per_cpu_ptr(tr->array_buffer.data, cpu)->disabled);
|
||||
ring_buffer_record_disable_cpu(tr->array_buffer.buffer, cpu);
|
||||
#ifdef CONFIG_TRACER_MAX_TRACE
|
||||
ring_buffer_record_disable_cpu(tr->max_buffer.buffer, cpu);
|
||||
|
|
@ -5089,7 +5088,6 @@ int tracing_set_cpumask(struct trace_array *tr,
|
|||
}
|
||||
if (!cpumask_test_cpu(cpu, tr->tracing_cpumask) &&
|
||||
cpumask_test_cpu(cpu, tracing_cpumask_new)) {
|
||||
atomic_dec(&per_cpu_ptr(tr->array_buffer.data, cpu)->disabled);
|
||||
ring_buffer_record_enable_cpu(tr->array_buffer.buffer, cpu);
|
||||
#ifdef CONFIG_TRACER_MAX_TRACE
|
||||
ring_buffer_record_enable_cpu(tr->max_buffer.buffer, cpu);
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user