From: Li Bin <huawei.libin@huawei.com>
To: <rostedt@goodmis.org>, <mingo@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, Li Bin <huawei.libin@huawei.com>,
"Tony Luck" <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>, <linux-ia64@vger.kernel.org>,
James Hogan <james.hogan@imgtec.com>,
<linux-metag@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
"Michael Ellerman" <mpe@ellerman.id.au>,
<linuxppc-dev@lists.ozlabs.org>, <linux-sh@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>, <x86@kernel.org>
Subject: [PATCH 0/5] ftrace: fix ftrace misleading comments for arch using it
Date: Fri, 4 Dec 2015 15:27:42 +0800 [thread overview]
Message-ID: <1449214067-12177-1-git-send-email-huawei.libin@huawei.com> (raw)
Fix the following similar misleading comments of ftrace for arch
ia64/metag/powerpc/sh/x86:
Note: Due to modules and __init, code can
disappear and change, we need to protect against faulting
as well as code changing. We do this by using the
probe_kernel_* functions.
No real locking needed, this code is run through
kstop_machine, or before SMP starts.
Cc: Tony Luck <tony.luck@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>
Cc: linux-ia64@vger.kernel.org
Cc: James Hogan <james.hogan@imgtec.com>
Cc: linux-metag@vger.kernel.org
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Cc: linux-sh@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>
"Cc: H. Peter Anvin" <hpa@zytor.com>
Cc: x86@kernel.org
Li Bin (5):
ia64: ftrace: fix the comments for ftrace_modify_code
metag: ftrace: fix the comments for ftrace_modify_code
powerpc: ftrace: fix the comments for ftrace_modify_code
sh: ftrace: fix the comments for ftrace_modify_code
x86: ftrace: fix the comments for ftrace_modify_code_direct
arch/ia64/kernel/ftrace.c | 13 ++++++-------
arch/metag/kernel/ftrace.c | 12 ++++++------
arch/powerpc/kernel/ftrace.c | 13 ++++++-------
arch/sh/kernel/ftrace.c | 13 ++++++-------
arch/x86/kernel/ftrace.c | 13 ++++++-------
5 files changed, 30 insertions(+), 34 deletions(-)
next reply other threads:[~2015-12-04 7:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 7:27 Li Bin [this message]
2015-12-04 7:27 ` [PATCH 3/5] powerpc: ftrace: fix the comments for ftrace_modify_code Li Bin
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=1449214067-12177-1-git-send-email-huawei.libin@huawei.com \
--to=huawei.libin@huawei.com \
--cc=benh@kernel.crashing.org \
--cc=fenghua.yu@intel.com \
--cc=james.hogan@imgtec.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-metag@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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).