From: Steven Rostedt <rostedt@goodmis.org>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: Have persistent trace instances save module addresses
Date: Fri, 21 Mar 2025 12:36:50 -0400 [thread overview]
Message-ID: <20250321123650.5042267c@batman.local.home> (raw)
In-Reply-To: <20250321155422.GA1290637@mit.edu>
On Fri, 21 Mar 2025 11:54:22 -0400
"Theodore Ts'o" <tytso@mit.edu> wrote:
> On Wed, Mar 05, 2025 at 11:45:45AM -0500, Steven Rostedt wrote:
> > For trace instances that are mapped to persistent memory, have them use
> > the scratch area to save the currently loaded modules. This will allow
> > where the modules have been loaded on the next boot so that their
> > addresses can be deciphered by using where they were loaded previously.
>
> Hi,
>
> When building against linux-next today, I found that this commit
> breaks builds when the kernel hasn't enabled CONFIG_MODULES. Could
> you please take a look?
>
> Many thanks!!
>
Yeah, Masami has a fix already. I've been traveling for OSPM and
haven't had the time to apply and test it.
-- Steve
https://lore.kernel.org/all/174230515367.2909896.8132122175220657625.stgit@mhiramat.tok.corp.google.com/
prev parent reply other threads:[~2025-03-21 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 15:54 [PATCH] tracing: Have persistent trace instances save module addresses Theodore Ts'o
2025-03-21 16:36 ` Steven Rostedt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250321123650.5042267c@batman.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.