From: Steven Rostedt <rostedt@goodmis.org>
To: Atish Patra <atishp@atishpatra.org>
Cc: Guo Ren <guoren@kernel.org>, Zong Li <zong.li@sifive.com>,
Paul McKenney <paulmck@kernel.org>,
josh@joshtriplett.org, mathieu.desnoyers@efficios.com,
jiangshanlai@gmail.com, joel@joelfernandes.org,
vincent.whitchurch@axis.com, Thomas Gleixner <tglx@linutronix.de>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Greentime Hu <greentime.hu@sifive.com>,
Colin Ian King <colin.king@canonical.com>,
rcu@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH] stop_machine: Mark functions as notrace
Date: Fri, 30 Oct 2020 20:28:18 -0400 [thread overview]
Message-ID: <20201030202818.72070cbd@oasis.local.home> (raw)
In-Reply-To: <CAOnJCULO7TuRhBcx6KUVr6t_jqouN-0rao9QXC1RgrU5ehutkw@mail.gmail.com>
On Fri, 30 Oct 2020 14:47:56 -0700
Atish Patra <atishp@atishpatra.org> wrote:
> > Look at arm64, they __kprobes flag and I guess it would also prevent
> > ftrace call site.
> >
>
> Are you sure about that ? __kprobes puts the code in .kprobes.text section
> which is under whitelist sections in recordmcount.pl & recordmcount.c.
Correct, ftrace can trace functions marked with __kprobes. That said,
the instruction you are looking at here, is in a file that is
blacklisted from recordmcount.
CFLAGS_REMOVE_insn.o = $(CC_FLAGS_FTRACE)
All ftrace flags are removed from the compiling of insn.c, and every
function in that file will not be traced.
-- Steve
next prev parent reply other threads:[~2020-10-31 0:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 7:38 Zong Li
2020-10-21 14:12 ` Steven Rostedt
2020-10-21 14:15 ` Steven Rostedt
2020-10-21 15:44 ` Paul E. McKenney
2020-10-21 15:54 ` Steven Rostedt
2020-10-21 16:16 ` Paul E. McKenney
2020-10-22 0:58 ` Atish Patra
2020-10-23 19:29 ` Colin Ian King
2020-10-26 2:56 ` Zong Li
2020-10-26 11:17 ` [tip: smp/urgent] stop_machine, rcu: " tip-bot2 for Zong Li
2020-10-28 15:44 ` [PATCH] stop_machine: " Guo Ren
2020-10-29 0:23 ` Atish Patra
2020-10-29 2:34 ` Zong Li
2020-10-29 16:06 ` Guo Ren
2020-10-29 18:46 ` Atish Patra
2020-10-30 3:28 ` Guo Ren
2020-10-30 21:47 ` Atish Patra
2020-10-31 0:28 ` Steven Rostedt [this message]
2020-10-31 7:42 ` Guo Ren
2020-11-03 15:33 ` Atish Patra
2020-11-06 2:44 ` Guo Ren
2020-10-29 16:01 ` Guo Ren
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=20201030202818.72070cbd@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=atishp@atishpatra.org \
--cc=colin.king@canonical.com \
--cc=greentime.hu@sifive.com \
--cc=guoren@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=palmerdabbelt@google.com \
--cc=paul.walmsley@sifive.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vincent.whitchurch@axis.com \
--cc=zong.li@sifive.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®