[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200327103046.08f06131@gandalf.local.home>
Date: Fri, 27 Mar 2020 10:30:46 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: David Laight <David.Laight@...LAB.COM>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
"Alexei Starovoitov" <alexei.starovoitov@...il.com>,
Peter Wu <peter@...ensteyn.nl>,
Jonathan Corbet <corbet@....net>,
Tom Zanussi <zanussi@...nel.org>,
"Shuah Khan" <shuahkhan@...il.com>, bpf <bpf@...r.kernel.org>
Subject: Re: [PATCH 00/12 v2] ring-buffer/tracing: Remove disabling of ring
buffer while reading trace file
On Fri, 27 Mar 2020 10:07:00 +0000
David Laight <David.Laight@...LAB.COM> wrote:
> > If needed, I can add a kernel command line option and a Kconfig that
> > makes this set to true by default.
>
> Maybe a different file 'trace_no_pause' ?
I rather not add another file, it adds more complexity, and confuses the
interface even more. I'll leave this as is.
> Along with the one that lets you read the raw trace and get EOF.
Can you explain this more? I think we talked about this before, but I don't
remember the details.
-- Steve
Powered by blists - more mailing lists