[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180207205501.2b19c8d6@gandalf.local.home>
Date: Wed, 7 Feb 2018 20:55:01 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Tom Zanussi <tom.zanussi@...ux.intel.com>
Cc: tglx@...utronix.de, mhiramat@...nel.org, namhyung@...nel.org,
vedang.patel@...el.com, bigeasy@...utronix.de,
joel.opensrc@...il.com, joelaf@...gle.com,
mathieu.desnoyers@...icios.com, baohong.liu@...el.com,
rajvi.jingar@...el.com, julia@...com, fengguang.wu@...el.com,
linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org
Subject: Re: [PATCH v9 35/37] tracing: Increase trace_recursive_lock() limit
for synthetic events
On Mon, 15 Jan 2018 20:52:09 -0600
Tom Zanussi <tom.zanussi@...ux.intel.com> wrote:
> static __always_inline int
> trace_recursive_lock(struct ring_buffer_per_cpu *cpu_buffer)
> {
> - if (cpu_buffer->current_context >= 4)
> + if (cpu_buffer->current_context >= 6)
I can't apply this patch because the new context counting broke tracing
suspend and resume because it depended on the context recursive locking.
Link: http://lkml.kernel.org/r/20180116020051.776011914@goodmis.org
I added the attached two patches which appear to do the job.
Let me know what you think.
-- Steve
View attachment "0001-ring-buffer-Add-nesting-for-adding-events-within-eve.patch" of type "text/x-patch" (4428 bytes)
View attachment "0001-tracing-Use-the-ring-buffer-nesting-to-allow-synthet.patch" of type "text/x-patch" (1970 bytes)
Powered by blists - more mailing lists