From: He Kuang <hekuang@huawei.com>
To: <masami.hiramatsu.pt@hitachi.com>
Cc: <ananth@in.ibm.com>, <linux-kernel@vger.kernel.org>,
<anil.s.keshavamurthy@intel.com>, <wangnan0@huawei.com>,
<hekuang@huawei.com>
Subject: [RFC]kprobes functionality with kernel-hacking disabled
Date: Fri, 19 Dec 2014 01:41:42 +0800 [thread overview]
Message-ID: <1418924502-7229-1-git-send-email-hekuang@huawei.com> (raw)
kprobes is so excellent in performance analysis. But in many practical
performance analysis scenarios, performance & debuging related configs
maybe disabled. So, we should recompile the kernel for further analysis,
this is not so convinient.
I've read this thread asked a question to use kprobes as a module
(https://lkml.org/lkml/2012/5/15/46), and know the ftrace dependence
issue. But when we meet a kernel compiled without CONFIG_KPROBES*,
the only thing we need is the basic kprobes funtionality, have ftrace
or not is not the major problem, in fact, most cases ftrace is disabled
too.
Do you have any advices on the conflicts between kernel hacking tools and
practical kernel which compiled without it? If there is no kprobes
module, what should we use?
Signed-off-by: He Kuang <hekuang@huawei.com>
--
1.7.9.5
reply other threads:[~2014-12-18 9:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1418924502-7229-1-git-send-email-hekuang@huawei.com \
--to=hekuang@huawei.com \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=wangnan0@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 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®