[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20231218182428.4469d2b3@gandalf.local.home>
Date: Mon, 18 Dec 2023 18:24:28 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: LKML <linux-kernel@...r.kernel.org>, Linux Trace Kernel
<linux-trace-kernel@...r.kernel.org>
Cc: Masami Hiramatsu <mhiramat@...nel.org>, Mark Rutland
<mark.rutland@....com>, Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Joel Fernandes <joel@...lfernandes.org>
Subject: Re: [PATCH v2] ring-buffer: Add interrupt information to dump of
data sub-buffer
On Mon, 18 Dec 2023 17:01:06 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:
> @@ -3347,7 +3418,8 @@ static void check_buffer(struct ring_buffer_per_cpu *cpu_buffer,
> }
> }
> if ((full && ts > info->ts) ||
> - (!full && ts + info->delta != info->ts)) {
> + (!full && ts + info->delta != info->ts) ||
> + e > 0xfa0) {
> /* If another report is happening, ignore this one */
> if (atomic_inc_return(&ts_dump) != 1) {
> atomic_dec(&ts_dump);
Oops, I accidentally committed the "add this to force a dump" code :-p
Will send a v3 soon.
-- Steve
Powered by blists - more mailing lists