[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20250206092855.6d313227cf5db2a1a96ac200@kernel.org>
Date: Thu, 6 Feb 2025 09:28:55 +0900
From: Masami Hiramatsu (Google) <mhiramat@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Luis Chamberlain
<mcgrof@...nel.org>, Petr Pavlu <petr.pavlu@...e.com>, Sami Tolvanen
<samitolvanen@...gle.com>, Daniel Gomez <da.gomez@...sung.com>,
linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
linux-modules@...r.kernel.org
Subject: Re: [PATCH v2 0/2] tracing: Introduce relative stacktrace
On Wed, 5 Feb 2025 17:52:34 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:
> On Wed, 5 Feb 2025 09:53:22 -0500
> Steven Rostedt <rostedt@...dmis.org> wrote:
>
> > On Wed, 5 Feb 2025 21:25:43 +0900
> > Masami Hiramatsu (Google) <mhiramat@...nel.org> wrote:
> >
> > > Anyway, let me try storing the module table.
> >
> > I have the module table code almost done. At least the recording of the
> > modules into persistent memory. Exposing and using it is not started yet. I
> > can send what I have and you can take it over if you want.
>
> I finished what I was working on. Can you start with that? I can push this
> up to the ring-buffer/core branch. Although it's not fully tested.
Oops, I also worked on that. Anyway, let me check it.
Thanks!
>
> -- Steve
>
--
Masami Hiramatsu (Google) <mhiramat@...nel.org>
Powered by blists - more mailing lists