[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230818232301.902ad9319569379ebd7df557@kernel.org>
Date: Fri, 18 Aug 2023 23:23:01 +0900
From: Masami Hiramatsu (Google) <mhiramat@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Zheng Yejian <zhengyejian1@...wei.com>, <laijs@...fujitsu.com>,
<linux-kernel@...r.kernel.org>,
<linux-trace-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] tracing: Introduce pipe_cpumask to avoid race on
trace_pipes
On Fri, 18 Aug 2023 09:41:28 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:
> On Fri, 18 Aug 2023 14:03:09 +0900
> Masami Hiramatsu (Google) <mhiramat@...nel.org> wrote:
>
> > Looks good to me.
> >
> > Reviewed-by: Masami Hiramatsu (Google) <mhiramat@...nel.org>
> >
> > BTW, this reminds me that splice read support had been introduced for
> > virtio-trace support. I've tested it with/without this patch, but I hit
> > a different issue, which seems like a virtio-serial issue (per-cpu buffers
> > on the guest are spliced correctly, but the data can not be read from host
> > side). Let me investigate it.
>
> Is virtio-trace using trace_pipe or trace_pipe_raw? Those two are handled
> differently.
It uses trace_pipe_raw. I guess if splice(from trace_pipe_raw to virtio-serial)
returns -1 and errno == EAGAIN, the trace data will be lost?
Thank you,
>
> -- Steve
--
Masami Hiramatsu (Google) <mhiramat@...nel.org>
Powered by blists - more mailing lists