Re: [ 54/68] tracing: change CPU ring buffer state fromtracing_cpumask

From: Herton Ronaldo Krzesinski
Date: Thu Jul 12 2012 - 21:47:54 EST


On Thu, Jul 12, 2012 at 04:02:28PM -0700, Greg Kroah-Hartman wrote:
> From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
>
> 3.0-stable review patch. If anyone has any objections, please let me know.
>
> ------------------
>
> From: Vaibhav Nagarnaik <vnagarnaik@xxxxxxxxxx>
>
> commit 71babb2705e2203a64c27ede13ae3508a0d2c16c upstream.
>
> According to Documentation/trace/ftrace.txt:
>
> tracing_cpumask:
>
> This is a mask that lets the user only trace
> on specified CPUS. The format is a hex string
> representing the CPUS.
>
> The tracing_cpumask currently doesn't affect the tracing state of
> per-CPU ring buffers.
>
> This patch enables/disables CPU recording as its corresponding bit in
> tracing_cpumask is set/unset.
>
> Link: http://lkml.kernel.org/r/1336096792-25373-3-git-send-email-vnagarnaik@xxxxxxxxxx

Missing patch.

>
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>

--
[]'s
Herton
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/