[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250102154146.1d5e8f9c@gandalf.local.home>
Date: Thu, 2 Jan 2025 15:41:46 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Peter Zijlstra <peterz@...radead.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>, Linus Torvalds
<torvalds@...ux-foundation.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 14/14] scripts/sorttable: ftrace: Do not add weak
functions to available_filter_functions
On Thu, 2 Jan 2025 21:32:00 +0100
Peter Zijlstra <peterz@...radead.org> wrote:
> This is quite the insane interface -- but whatever. I still feel
> strongly you should fix kallsyms so that we can all deal more sanely
> with the weak crap.
Question about fixing kallsyms, which I would like done too. I guess an
invisible place holder for weak functions may be best. Saving the size of
all functions could be memory wasteful. As there are a lot of functions:
# wc -l /proc/kallsyms
207126 /proc/kallsyms
What would be best? To add a placeholder where weak functions are, but they
would not be printed in /proc/kallsyms? If a lookup occurs, and it lands
on one of theses functions, to return "not found"?
-- Steve
Powered by blists - more mailing lists