From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: systemtap@sourceware.org
Subject: Re: [PATCH -tip v11 0/7] kprobes: NOKPROBE_SYMBOL for modules, and scalbility efforts
Date: Thu, 16 Jul 2015 02:44:00 -0000 [thread overview]
Message-ID: <55A71A9D.10603@hitachi.com> (raw)
In-Reply-To: <loom.20150709T130940-101@post.gmane.org>
On 2015/07/09 20:40, Pratyush Anand wrote:
> Hi Masami,
>
> Masami Hiramatsu <masami.hiramatsu.pt <at> hitachi.com> writes:
>
>>
>> Hi,
>> Here is the version 11 of NOKPROBE_SYMBOL/scalability series.
>> This fixes some issues.
>
> If I have not missed then v11 seems the last version posted for this series.
> However, I do not see any ACK/NACK for the series. So, I am just curious
> that why didn't it got merged into upstream.
Yeah, that is still not merged yet.
> It seems a useful series and without these patches system becomes extremely
> slow with large number of kprobes enabled.
Yes, I should revise it for the latest kernel...
>
> When I enabled massive kprobes [1] on my ARM64 system without this patch
> series, I see "NMI watchdog: BUG: soft lockup" for all CPUs even before all
> kprobes are enabled. However, If I use these patches then system is able to
> survive and I can see following output for script [1].
>
> real 1m49.734s
> user 0m0.000s
> sys 0m53.950s
> 31364 kprobes enabled :-)
Wow! really nice result!!
>
> I was able to run `usex -e` to load the system, although I see that system
> is mostly occupied by kernel (97%).
>
> * Unix System EXerciser * USER SYSTEM IDLE LOADAVG TASKS/RUN TEST TIME *
> * USEX Version 1.9-36 * 3% 97% 0% 24.58 232/27 000:02:49 *
I see, since every function calls are interrupted by kprobes...
BTW, have you ever tried to analyze hot spot by using perf?
Thank you!
>
> ~Pratyush
>
> [1]
> #!/bin/sh
> grep ' [tT] ' /proc/kallsyms | fgrep -v '[' | awk '{print $3}' > syms.list
> echo 0 > /sys/kernel/debug/tracing/events/enable
> echo 0 > /sys/kernel/debug/tracing/events/kprobes/enable
> echo > /sys/kernel/debug/tracing/kprobe_events
> for i in `cat syms.list`;
> do
> echo "p $i" >> /sys/kernel/debug/tracing/kprobe_events ;
> done
> time echo 1 > /sys/kernel/debug/tracing/events/kprobes/enable
> num_kprobe=`cat /sys/kernel/debug/tracing/kprobe_events | wc -l`
> echo "$num_kprobe kprobes enabled :-)"
>
>
>
>
>
--
Masami HIRAMATSU
Linux Technology Research Center, System Productivity Research Dept.
Center for Technology Innovation - Systems Engineering
Hitachi, Ltd., Research & Development Group
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2015-07-16 2:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 8:20 Masami Hiramatsu
2014-05-14 8:20 ` [PATCH -tip v11 1/7] kprobes: Support blacklist functions in module Masami Hiramatsu
2014-05-14 8:21 ` [PATCH -tip v11 7/7] ftrace: Introduce FTRACE_OPS_FL_SELF_FILTER for ftrace-kprobe Masami Hiramatsu
2014-05-14 8:21 ` [PATCH -tip v11 5/7] kprobes: Enlarge hash table to 512 entries Masami Hiramatsu
2014-05-14 8:21 ` [PATCH -tip v11 6/7] kprobes: Introduce kprobe cache to reduce cache misshits Masami Hiramatsu
2014-05-14 8:21 ` [PATCH -tip v11 4/7] kprobes/x86: Remove unneeded preempt_disable/enable in interrupt handlers Masami Hiramatsu
2014-05-14 8:21 ` [PATCH -tip v11 3/7] kprobes/x86: Use kprobe_blacklist for .kprobes.text and .entry.text Masami Hiramatsu
2014-05-14 8:21 ` [PATCH -tip v11 2/7] kprobes: Use NOKPROBE_SYMBOL() in sample modules Masami Hiramatsu
2015-07-09 11:50 ` [PATCH -tip v11 0/7] kprobes: NOKPROBE_SYMBOL for modules, and scalbility efforts Pratyush Anand
2015-07-16 2:44 ` Masami Hiramatsu [this message]
2015-07-16 8:59 ` Pratyush Anand
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=55A71A9D.10603@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).