[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250812152247.6a5a4ed1@gandalf.local.home>
Date: Tue, 12 Aug 2025 15:22:47 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Douglas Raillard <douglas.raillard@....com>
Cc: Steven Rostedt <rostedt@...nel.org>, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, Masami Hiramatsu <mhiramat@...nel.org>,
Mark Rutland <mark.rutland@....com>, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>, Andrew Morton
<akpm@...ux-foundation.org>, Peter Zijlstra <peterz@...radead.org>,
Namhyung Kim <namhyung@...nel.org>, Takaya Saeki <takayas@...gle.com>, Tom
Zanussi <zanussi@...nel.org>, Thomas Gleixner <tglx@...utronix.de>, Ian
Rogers <irogers@...gle.com>, aahringo@...hat.com
Subject: Re: [PATCH 2/7] tracing: Have syscall trace events show "0x" for
values greater than 10
On Wed, 6 Aug 2025 17:42:38 +0100
Douglas Raillard <douglas.raillard@....com> wrote:
>
> AFAIK to this day, there is no tool providing a simple script/SQL interface
> to a trace.dat file beyond basic filtering like trace-cmd report. I've had this
Well, I did have this patch that I never applied:
https://lore.kernel.org/all/20200116104804.5d2f71e2@gandalf.local.home/
-- Steve
Powered by blists - more mailing lists