[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250102144718.51689c71@gandalf.local.home>
Date: Thu, 2 Jan 2025 14:47:18 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
linux-kbuild@...r.kernel.org, bpf <bpf@...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>,
Masahiro Yamada <masahiroy@...nel.org>, Nathan Chancellor
<nathan@...nel.org>, Nicolas Schier <nicolas@...sle.eu>, Zheng Yejian
<zhengyejian1@...wei.com>, Martin Kelly <martin.kelly@...wdstrike.com>,
Christophe Leroy <christophe.leroy@...roup.eu>, Josh Poimboeuf
<jpoimboe@...hat.com>
Subject: Re: [PATCH 00/14] scripts/sorttable: ftrace: Remove place holders
for weak functions in available_filter_functions
On Thu, 2 Jan 2025 14:45:53 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:
> > Why even do that? Why not just make the mcount_loc table be proper in
> > the first place.
>
> I was a bit nervous about changing the stop_mcount_loc value. I thought of
> doing that first, but then I noticed that the value is found by looking at
> the System.map file and not from the object itself. Changing it in the
> object will require some more elf parsing. Just zeroing out didn't require
> that.
I could still zero it out, but then change the start_mcount_loc to the
first valid function after the sort. As all the zeros will be at the start.
-- Steve
Powered by blists - more mailing lists