From: Heiko Carstens <hca@linux.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org, bpf <bpf@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-s390@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>,
Zheng Yejian <zhengyejian1@huawei.com>,
Martin Kelly <martin.kelly@crowdstrike.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>
Subject: Re: [PATCH v4 0/6] scripts/sorttable: ftrace: Remove place holders for weak functions in available_filter_functions
Date: Fri, 21 Feb 2025 10:42:51 +0100 [thread overview]
Message-ID: <20250221094251.11661Ada-hca@linux.ibm.com> (raw)
In-Reply-To: <20250219102220.3b79ec5e@gandalf.local.home>
On Wed, Feb 19, 2025 at 10:22:20AM -0500, Steven Rostedt wrote:
> On Tue, 18 Feb 2025 15:58:36 +0100
> Heiko Carstens <hca@linux.ibm.com> wrote:
> > > This series removes the place holder __ftrace_invalid_address___ from
> > > the available_filter_functions file.
> > >
> > > The rewriting of the sorttable.c code to make it more manageable
> > > has already been merged:
> > >
> > > https://git.kernel.org/torvalds/c/c0e75905caf368e19aab585d20151500e750de89
> > >
> > > Now this is only for getting rid of the ftrace invalid function place holders.
> >
> > Since you asked me to test this on s390: seems to work with
> > HAVE_BUILDTIME_MCOUNT_SORT enabled; the ftrace selftests still
> > work as before.
>
> Great!
>
> I'm guessing by just adding the support in s390 with what is upstream as
> well as what is in my for-next would work?
Yes, both variants work.
> You can just add that for the next merge window then.
It is already in linux-next:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=fa1518875286c94111bdaf1c7bae188c9c426c6b
Thanks for making aware of this!
prev parent reply other threads:[~2025-02-21 9:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 15:34 [PATCH v4 0/6] scripts/sorttable: ftrace: Remove place holders for weak functions in available_filter_functions Steven Rostedt
2025-02-17 15:34 ` [PATCH v4 1/6] arm64: scripts/sorttable: Implement sorting mcount_loc at boot for arm64 Steven Rostedt
2025-02-17 15:34 ` [PATCH v4 2/6] scripts/sorttable: Have mcount rela sort use direct values Steven Rostedt
2025-02-17 15:34 ` [PATCH v4 3/6] scripts/sorttable: Always use an array for the mcount_loc sorting Steven Rostedt
2025-02-17 15:34 ` [PATCH v4 4/6] scripts/sorttable: Zero out weak functions in mcount_loc table Steven Rostedt
2025-02-17 15:34 ` [PATCH v4 5/6] ftrace: Update the mcount_loc check of skipped entries Steven Rostedt
2025-02-17 15:34 ` [PATCH v4 6/6] ftrace: Have ftrace pages output reflect freed pages Steven Rostedt
2025-02-18 14:58 ` [PATCH v4 0/6] scripts/sorttable: ftrace: Remove place holders for weak functions in available_filter_functions Heiko Carstens
2025-02-18 19:56 ` Steven Rostedt
2025-02-19 15:22 ` Steven Rostedt
2025-02-21 9:42 ` Heiko Carstens [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=20250221094251.11661Ada-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=gor@linux.ibm.com \
--cc=jpoimboe@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.kelly@crowdstrike.com \
--cc=masahiroy@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.org \
--cc=zhengyejian1@huawei.com \
/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.