From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
Steven Rostedt <rostedt@goodmis.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
linuxppc-dev@lists.ozlabs.org, llvm@lists.linux.dev,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] ftrace/recordmcount: Handle object files without section symbols
Date: Thu, 28 Apr 2022 22:49:50 +0530 [thread overview]
Message-ID: <cover.1651166001.git.naveen.n.rao@linux.vnet.ibm.com> (raw)
This is v2 of the series posted at:
http://lkml.kernel.org/r/cover.1651047542.git.naveen.n.rao@linux.vnet.ibm.com
For v2, the first patch is slightly modified to skip the loop, rather
than depending on addr == 0 to do so. The second patch is updated to
make this behavior be opt-in by architectures so that they can validate
the read mcount locations.
- Naveen
Naveen N. Rao (2):
ftrace: Drop duplicate mcount locations
ftrace: recordmcount: Handle sections with no non-weak symbols
Makefile | 4 ++
arch/powerpc/Kconfig | 1 +
arch/powerpc/include/asm/ftrace.h | 8 +--
arch/powerpc/kernel/trace/ftrace.c | 11 ++++
kernel/trace/Kconfig | 6 ++
kernel/trace/ftrace.c | 13 ++++-
scripts/Makefile.build | 3 +
scripts/recordmcount.c | 6 +-
scripts/recordmcount.h | 94 ++++++++++++++++++++++++++----
9 files changed, 125 insertions(+), 21 deletions(-)
base-commit: 83d8a0d166119de813cad27ae7d61f54f9aea707
--
2.35.1
next reply other threads:[~2022-04-28 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 17:19 Naveen N. Rao [this message]
2022-04-28 17:19 ` [PATCH v2 1/2] ftrace: Drop duplicate mcount locations Naveen N. Rao
2022-04-28 17:19 ` [PATCH v2 2/2] ftrace: recordmcount: Handle sections with no non-weak symbols Naveen N. Rao
2022-04-28 22:42 ` Steven Rostedt
2022-04-29 17:39 ` Naveen N. Rao
2022-04-29 17:59 ` Steven Rostedt
2022-04-29 19:33 ` Naveen N. Rao
2022-04-29 19:47 ` Steven Rostedt
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=cover.1651166001.git.naveen.n.rao@linux.vnet.ibm.com \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=mpe@ellerman.id.au \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=rostedt@goodmis.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).