[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240415044431.308f2e09@rorschach.local.home>
Date: Mon, 15 Apr 2024 04:44:30 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Luca Ceresoli <luca.ceresoli@...tlin.com>
Cc: Masami Hiramatsu <mhiramat@...nel.org>, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>, Thomas Petazzoni
<thomas.petazzoni@...tlin.com>
Subject: Re: TP_printk() bug with %c, and more?
On Mon, 18 Mar 2024 16:43:07 +0100
Luca Ceresoli <luca.ceresoli@...tlin.com> wrote:
> However the arrows are still reversed.
This requires a kernel change. The problem is that the print fmt has:
print fmt: "%c%s %s %s %s %s", (int) REC->path_node && (int) REC->path_connect ? '*' : ' ', __get_str(wname), (((REC->path_dir) == SND_SOC_DAPM_DIR_OUT) ? "->" : "<-"), __get_str(pname), (((REC->path_dir) == SND_SOC_DAPM_DIR_OUT) ? "->" : "<-"), __get_str(pnname)
User space (trace-cmd and perf) have no idea what SND_SOC_DAPM_DIR_OUT
is. The kernel needs to convert that, otherwise the parsing will fail,
or it will default it to zero.
-- Steve
Powered by blists - more mailing lists